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