[00:16] btw knome, re https://screenshots.debian.net/, I was thinking in using the same screenshot standardization we use for all the xfce4 related documentation [00:17] sounds good [00:17] the standard we use is here if you want to check it -> http://smdavis.us/doku/doku.php?id=playground:sceenshot-stds [00:17] ok [00:20] Today's report from me: http://paste.openstack.org/show/EJHLelJVbldtkzt38JH0 [00:22] Unit193 did you ever get to try to fix with the translations credits issue? [00:22] s/fix with/fix [00:23] Not really, either going to have to find someone that might know what's up, or revert that and just keep it for the website build. [00:24] that would be the sane approach [00:25] I mean if we don't manage to get it working, it makes no sense to have it in the documentation [00:25] It works, just not in the package build. :D [00:25] well, we still have a lot of time before dropping it [00:27] i'd say we still have a lot of time to fix it :P [00:27] we'll assess it near documentation freeze [00:28] of course this is if it's not fixed by then [00:31] But, someone would be needed to fix it first, before it's fixed. It currently works, and the build-depends pull in gettext and everything seemingly important, heck I even dropped in 'locales', but no luck... [00:31] Thus, poke of the Sean happened, since lead dev and all. :P [00:42] bluesabre, as soon as you have a moment to spare can you please take a look at ^^^ [00:42] :P [01:02] hey slickymaster [01:03] hey bluesabre [01:03] whats up? [01:04] it's about the translation credits in the documentation [01:04] ah, Unit193: you couldn't fix them? [01:04] yeaps, that's about it [01:04] Still don't know what's missing. [01:04] :( [01:05] as soon as humanly possible can you take a look at it bluesabre? [01:05] pretty please, with sugar on top [01:05] yeah, will take a look tonight [01:05] so, where does it fail? [01:06] Unit193 would be the one to enlighten on that [01:10] ok, i'm so ready to bed; looked at the last line, and the "enlighten" word looked like some RTL (arabic?) language [01:10] nighty, and talk to you all later [01:10] Ahaha, g'night. :) [01:11] bluesabre, and thanks for the compliments [01:11] --> [01:11] nighty [01:11] ?? [01:14] And I suppose I should respond, scripts/translators.sh: The TEXTDOMAINDIR=$CURDIR/mo/ LANGUAGE=$lang stuff doesn't appear to work, but then I haven't run it with echo everywhere either. [02:44] patched thunar for utopic in the -staging ppa [07:19] ochosi: so today it was obviously xfsettingsd crash, not sure why restarting xfsettingsd works for everything but xchat [08:54] elfy: not sure tbh [08:54] haven't used xchat in a while [08:55] wild guess: it's relying on some ancient gtk3 routines which meant that a programme had to be restarted in order for theme-changes to take effect [08:55] (rather speculative though, because i'd assume that it'd be fixed in gtk3 for all gtk3 apps at once, but you know, xchat is rather unmaintained) [10:46] elfy: there is a good possibility the code sets the theme on its own, or somehow blocks its event. I know an event is triggered when icon themes change [10:48] ochosi: was it traffic-light that you wanted me to take a look at? [10:48] yup [10:50] eh, not really a fan of those colors at least [10:51] I think I prefer the way numix uses the selection color there [10:51] you'd prefer violet for closing, turquoise for minimizing and pink for maximizing? :) [10:52] iirc i did the same thing for numix that i did for greybird [10:52] picking up the theme colors [10:52] (although i don't remember now whether i ended up implementing that for greybird after all) [10:53] current greybird is just grey, numix is blue since I am still using greybird as the gtk theme [10:54] yeah, blue would be possible, but since everything is already so blue... [10:54] either we give the colors a meaning or we stick with what we got, is my general stance [10:55] yeah, I'd learn towards keeping the grey [10:55] *lean [10:57] btw, seems like the evince visual corruption doesn't occur in unity, but an upcoming gtk3-backport-fix for utopic might fix it [10:57] also, i asked robert about not using headerbars in simplescan for xubuntu [10:57] and he said he'll patch that in [10:57] (already linked to bugs blueprint) [10:58] ah [10:59] I wasn't complaining there... they actually aren't so bad [11:00] They're not quite as great as they are mentioned in OMGUbuntu "HeaderBars unify the window bar, title bar and toolbar into one, saving a huge amount of wasted vertical and horizontal space in the process." [11:01] but they're not inherently bad, xfce does well with them [11:15] yeah [11:16] i know, but in terms of consistency it's probably better this way [11:16] i'd rather switch to headerbars across our gtk3 apps, evince, file-roller, calc etc than having one app standing out [11:16] we can consider this until the next LTS or even test it for one release if you guys are up for it [11:18] is it because of the patching that file-roller has consistently had two menubars for a while? [11:19] i guess so [11:20] * bluesabre hopes for a fully functional squeeze release in the near future :) [11:21] you're an optimist :) [11:22] gah, really, that is a bit annoying. some folks complaining that music playback at the lockscreen is a potential loss of privacy... [11:22] why can't those people simply hit the pause button then, i wonder [11:23] in xubuntu? [11:24] it [11:24] it's an issue submitted against light-locker [11:24] thats dump [11:24] dumb too [11:24] lol [11:25] you can always argue that leaving your pc (eg. not carrying it with you at all times) is a potential loss off privacy [11:25] somebody might see your pc! [11:25] zomg! [11:30] :) [12:20] ochosi: well - used hexchat since it crashed and all's appearing to be well [12:20] so - mark that one of as an SEP :) [14:39] elfy: SEP? [14:39] someone else's problem :) [14:40] Unit193: just checking that core(s) are still working [14:41] ah hehe [14:42] I knew xchat was unmaintained - just wanted to make sure it wasn't *us* [14:42] :) [14:42] especially if I'm using staging *things* [14:42] yeah, actually it really isn't our problem, unless we decide to go back to it [14:43] so far i haven't heard a single peep about xchat missing [14:43] and hexchat doesn't do the same - so even if people do ask - point them at the maintained one [14:43] although people seem to be incredibly slow at picking those sort of changes up (see today's sudden arousal wrt synaptic) [14:44] ochosi: well - that could be 1 or 2 things - people gave up and installed some other OS or just given up commenting :D [14:44] unlike me ;) [14:44] yea - the synaptic one made me lol a bit, not getting involved in that one - I install synaptic :p [14:45] sure, me too :) [14:45] but: xubuntu != ochosi's software selection [14:45] nope :) [14:45] same goes for every other individual in our team [14:45] of course [14:46] btw, if/when you need help with the incentives programme, lemme know [14:46] i kinda hope you can sort it out with p and k [14:47] but yeah, i'm around, is what i'm sayin [14:47] Also I install it, but use the other one. :P [14:47] well - we really just need to get it finalised tbh and then onto x.org then *we* can mention it elsewhere [14:47] could you link me to your QA processes pad again that you wanted me to review? [14:47] ochosi: ack [14:47] Unit193: you're weird, but we like you :p [14:48] other = apt/apt-get/apt-cache! [14:48] ochosi: http://pad.ubuntu.com/xubuntu-qa-v-cycle [14:48] thanks elfy [14:48] ochosi: and re incentive thing - once we start - your the final "Yep" for whoever gets it [14:49] ochosi: it's at the bottom of the pad [14:51] heh, actually sticking to the freeze schedule sounds like a good idea (still kinda amuses me every time i read it) [14:51] he he [14:59] elfy: quick question... [14:59] when bugs are reported from iso-testing, where/how do we collect/review them? [14:59] and when would we link them to our bug-blueprint? [15:00] i'm wondering whether it's a good idea to point people to that blueprint, as they might start to add their favorite bugreport there [15:00] but then again, we might have to try to pick up the new bugreports by hand and take them there [15:02] well ... [15:02] I check what's reported on both trackers - weed out the ones which are either not us, should be testcase, then see if I can reproduce [15:03] if I can't I'll see if the same thing shows up again [15:03] if it doesn't I'll ignore it [15:03] if I CAN reproduce it I'll talk about it in here with whoever [15:03] ok, that sounds great actually [15:04] and then it might get onto the bug blueprint [15:04] i've finished reading the document now, +1 from my side [15:04] ochosi: up to a point yea it is as we don't see the "the installer dialogue is too big" things in here :) [15:05] and if I miss a few days - trying to get history from the tracker is seriously bad news ;) [15:05] thanks :) [15:06] thank you for drafting it! [15:06] welcome [15:07] just so long as it is understood I'll ignore it :p [15:07] just so long as it is ignored I'll understand it [15:07] * ochosi is confused [15:08] I can go with either :) [15:08] :) [15:23] slickymasterWork, in "managing-applications.xml", we might want to further notice that setting the notifications for new releases to "never" is never recommended. maybe with a warning box [15:23] slickymasterWork, and we might want to point to the migrating section there [15:24] slickymasterWork, and potentially drop the "other options" subsection, that seems unnecessary since the user can obviously see those in the GUI themself; or alternatively, extend that subsection a bit [15:40] * sidi pats knome on the head [15:53] ok, knome [15:53] I'll take a look at it tonight [16:06] bah [16:07] booted 14.10 to verify that thunar SRU and it wasn't available yet :( [16:07] hi eric_the_idiot [16:07] hi [16:08] we eric_the_idiot [16:08] damn auto-complete [16:08] wb elfy [16:09] and eric_the_idiot (for that matter) [16:09] heh [16:09] hah [16:09] and hi as well :) [16:09] well I hope that's wb eric and not damn eric :p [16:10] sidi, silly steve [16:10] and silly elfy also [16:10] :P [16:10] :) [16:12] silly is good. [16:13] yay for that :) [16:18] Because we all are... [16:20] hhe [16:20] Unit193: so 64bit core installed ok in vivid [16:22] Okay, is it not expected to? :P [16:23] Good to know, do you have a package list by chance? [16:23] dpkg-query -W --showformat='${Installed-Size}\t${Package}\n' | sort -nr > manifest.list [16:27] I'd obviously have exactly that by chance ... [16:27] Unit193: I'll boot it again - just for you :) [16:27] elfy: You don't have to, really. [16:36] http://pastebin.ubuntu.com/8821359/ [16:36] but I did anyway ;) === GridCube is now known as CubeGrid === CubeGrid is now known as GridRegularPolyh === GridRegularPolyh is now known as GridCube [20:00] well for better or worse - the first QA mail has gone to the list now the trackers are up again [20:00] * Unit193 sees it. [20:01] "Hello all, been a while - or actually not" :P [20:01] :) [20:02] I don't get why people don't get program bug != testcase bug. [20:02] * elfy neither [20:04] And, I suppose if -testers only means I get emails twice, guess might as well remove that. [20:10] well - there are ~30 people in -testers - I wish they did [20:10] there are 8 in -qa - I wish they did too ;) [20:28] bluesabre ochosi: interested in panel wrapper crash reports ? [20:29] wrapper-2.0 crashed with SIGSEGV in strrchr() [20:41] bluesabre: thunar 1.6.3-1ubuntu6 in utopic-proposed [20:42] Hrm, what else do we have sitting in *-proposed? [20:43] bluesabre: shouldn't it be 1.6.3-1ubuntu5.1? not sure if this matters [20:44] Unit193: xfdesktop 4.11.8 (trusty) [20:44] Ah, that's the other one. Could only think of apt-offline. :P [20:46] apt-offline.. does anyone use this? [20:46] skellat seems to. [20:46] does anyone use abiword? [20:46] And I've helped a couple people with it, but that was network issues. [20:46] * elfy starts that for the vampire cycle :p [20:46] elfy: SkippersBoss does. :P [20:47] ha ha ha - oh yea :) [20:47] abiword was/is not broken in utopic, that's an improvement [20:47] usually there was always something wrong with it [20:50] indicator panel is crashing again [20:52] I did not mention this yet, but the vbox vt problem is not reproducible with vmware :) [20:53] Hah, niiice. [20:53] KVM/Qemu? [20:54] I did not test that [20:54] no it's not reproducible in that [20:55] I've just configured vmware on my windows 10 test system [20:55] it's just vb afaik [20:55] I knew that weeks ago :p [20:57] elfy: are you already testing thunar from utopic-proposed? [20:57] it needs to be verified [20:58] not yet - looked earlier, neither 32 or 64 have actually built yet [20:58] and to look at it I need to boot utopic - so won't be looking again today [20:58] ok, no need to hurry [20:58] utopic is at least all updated ready to look at some point tomorrow [20:59] armhf and ppc64el built. :P [20:59] yea :) [21:00] * Unit193 scratches head at lp 1343159. [21:00] Launchpad bug 1343159 in apt-offline (Ubuntu) "apt-offline get doesn't work on FreeBSD 10/Python 2.7.6" [Undecided,New] https://launchpad.net/bugs/1343159 [21:01] elfy: wrapper-2.0 is the indicator stuff [21:01] or to be more concrete, wrapper-2.0 is for gtk3 [21:01] ochosi: yea realised that eventually :) [21:01] and the only gtk3 plugin we have atm is for the indicators [21:02] but yeah, if the indicators go bad again it's good to know asap [21:02] ok - well I can add ind panel back and report it right now I suspect :p [21:03] ok thanks [21:03] d'oh [21:04] apport's not turned on properly yet it seems [21:04] :/ [21:05] well, give it some time then, it's ok i guess [21:05] although if you have some error message that makes sense, feel free to paste it [21:05] just seeing if I Can remember how to force it :) [21:06] mmm it is on [21:07] ok cool [21:10] no - I mean apport is on, but it's not sending to LP :) [21:13] oh [21:13] yep - got it :) [21:14] had to force apport to include crashes [21:15] Unit193: looks like maybe that bug should really go upstream... I don't see the connection to Ubuntu [21:15] I'll not write anything much on this bug for the moment ochosi [21:15] dkessel: Quite so, just found it weird so had to link to it. :D [21:16] :D [21:17] elfy: sure, let's keep this sorta thing on the radar, that's good enough for now [21:17] grrrr [21:17] so it's decided that the bug is private lol [21:18] ochosi: ok here you go bug 1389400 [21:18] bug 1389400 in xfce4-panel (Ubuntu) "wrapper-2.0 crashed with SIGSEGV in strrchr()" [Undecided,New] https://launchpad.net/bugs/1389400 [21:19] linked to blueprint so we've got one linked there at least [21:33] elfy: could you add in what indicators you're using? [21:33] no [21:34] i mean which ones are installed [21:34] it keeps crashing lol - can't add it :) [21:34] but I don't add anything - so it's just the default ones we have [21:34] sound/messaging and ... [21:35] ochosi: any others - without me searching :) [21:35] oh nvm - I'll just see what are installed from dpkg [21:35] dpkg -l | grep indicator- application is my guess. [21:35] Unit193: yea:) [21:37] done that then [21:37] elfy: you could try to uninstall one after the other until you can add it again [21:37] maybe we can narrow it dow [21:37] n [21:38] ok - well see comment in -offtopic - I'll make a note to do that tomorrow/manana :) [21:41] ochosi: I've made a note to do that - off now [22:43] slickymaster: Saved for a later network-manager date: nm-tool => `nmcli dev list` [22:46] ok thanks Unit193 [22:46] (That was more for me to grep than you to remember though. :P ) [22:47] that menas that is pretty much dateless, right? [22:47] xs/menas/means [22:48] Well, hopefully soon, but we'll see. [22:48] :)