[03:58] <bluesabre> dkessel: not yet... hopefully early this week
[08:40] <elfy> morning all
[09:09] <ochosi> morning
[09:11] <elfy> hi ochosi 
[09:33] <dkessel> morning :)
[11:55] <slickymasterWork> elfy, can you please try to reproduce bug 1391123
[12:00] <brainwash> slickymasterWork: appears to be the same crash bug 1389840
[12:00] <brainwash> caused by the vbox guest additions
[12:06] <elfy> mmm 
[12:07] <elfy> well - first log files appear to open with mousepad now - which is better and probably more expected
[12:07] <elfy> second can't reproduce currently - will try with guest additions installe
[12:07] <slickymasterWork> yes brainwash, apparently VBoxOGLpackspu.so seems to be the culprit
[12:07] <elfy> if it is another vbox bug then I am intending to completely ignore vb bugs this cycle :p
[12:08] <slickymasterWork> that seems reasonable elfy 
[12:08] <brainwash> or test without the guest additions
[12:10] <slickymasterWork> brainwash, testing without the guest additions is a nightmare as you only get a 800x600 screen
[12:10] <elfy> works fine here with vbox 
[12:11] <slickymasterWork> it could be something related to my vbox guest additions package 
[12:11] <slickymasterWork> I'll download today's image at lunch and will reset a new box
[12:11] <elfy> I have 4.3.18_96516
[12:12] <slickymasterWork> this one is 4.3.12
[12:12] <slickymasterWork> I'll also upgrade it
[12:13] <elfy> yep
[12:15] <elfy> and log files open in mousepad - must have changed - making testcase wrong - I'll follow up on that a bit later this afternoon
[12:41] <brainwash> bluesabre: will you fix the weather-plugin in precise? someone in my class was really upset about it not being fixed in precise yet
[12:41] <brainwash> I mean, precise is still supported after all
[12:41] <bluesabre> brainwash: yeah, we can try to backport a brand new version to precise. It's been broken a lot longer since the code is completely different and it uses a different API
[12:42] <knome> please keep in mind that precise isn't supported for very long and adjust the amount of work you're ready to put into it accordingly
[12:42] <bluesabre> that one won't be a patch unless somebody wants to write it, will try to release the new version instead... that might introduce more regressions
[12:43] <bluesabre> dkessel: let me know if there are any hooks or anything that need to be added to catfish, or if the updated widget names should be enough.  Will try to get to that tonight as possible
[12:44] <brainwash> sadly we cannot force people to upgrade to 14.04
[12:44] <bluesabre> brainwash: but we can advise that they transition to it before 12.04 becomes EOL
[12:45] <bluesabre> heading out now, bbl
[12:45] <knome> brainwash, we cannot force people to not use xubuntu 9.10 either, but that doesn't mean we should support/fix a broken application in it
[12:48] <ochosi> i guess the main point is that we're talking about a *weather* plugin for the panel
[12:48] <knome> i don't know what that was supposed to mean :)
[12:48] <knome> (whether you thought it's important, or not)
[12:49] <ochosi> it's really not our core interest, we don't ship it in our default install and people can still do pretty much everything with their systems without it
[12:50] <brainwash> nah, the point is that it's fixed in trusty and newer, that's the reason why a person complained about it
[12:50] <brainwash> he still uses precise
[12:53] <brainwash> slickymasterWork: what happened to your abiword crash report? :D
[12:54] <slickymasterWork> penalvch blew it :P
[12:55] <brainwash> maybe you should assign the parole one to vbox and mark the abiword one as duplicate
[12:56] <brainwash> some vbox dev needs to get involved here
[12:56] <knome> brainwash, maybe you really should get the bug team membership...
[12:56] <slickymasterWork> yeah, that sounds like a sane plan
[12:56] <slickymasterWork> lol
[12:56] <brainwash> hmpf
[12:56] <slickymasterWork> hey knome 
[12:57] <elfy> maybe you should wait and see if you can reproduce on newer vbox :)
[12:57]  * slickymasterWork is now known as the depinkifier man
[12:58] <slickymasterWork> of course elfy ;)
[12:58] <knome> :P
[13:00] <elfy> just run the mime testcase and passed it ;)
[13:01] <elfy> depinkify \o/
[13:53] <dkessel> bluesabre: I guess the widget names should be enough
[14:08] <jjfrv8> elfy, I think I found a bug in xfce4-mime-settings while doing the testcase. Do you know how I file a bug against that? It's not a package.
[14:12] <brainwash> jjfrv8: it's part of xfce4-settings
[14:13] <brainwash> and don't forget to forward the bug to the upstream bug tracker :)
[14:16] <jjfrv8> Thx.
[14:16] <brainwash> maybe it's even a known issue
[14:17] <jjfrv8> maybe but I confirmed it was not present in Trusty
[14:31] <ochosi> just received the news that status.ubuntu.com will be live soon for 15.04
[14:54] <jjfrv8> reported bug 1391184
[18:08] <slickymasterWork> so, elfy I'm not sure to what part of the test is jjfrv8 referring in bug 1391184
[18:09] <slickymasterWork> do you think he is referring to this section of the test: "This test will check that MIME Type Editor will correctly display a file association changed with another application"?
[18:09] <slickymasterWork> eric_the_idiot:  ^^
[18:10] <slickymasterWork> ups, not eric_the_idiot you crazy autocomplete, it's elfy 
[18:10] <knome> both idiot and crazy?
[18:10]  * knome hides
[18:10] <elfy> when you change app - it sets that field to something other than default - used to say User Set
[18:10] <elfy> now it doesn't - whether that is a bug or new behaviour I've not looked at yet
[18:11] <elfy> I am
[18:11] <slickymasterWork> because if it's that, whatI'm getting is yeah, but in step 2 if that section what I'm getting is Mousepad, not Abiword
[18:11] <elfy> idiot for putting up with the crazies :)
[18:12] <elfy> slickymasterWork: well - I don't know as I haven't nor am I intending too, memorised the testcases :)
[18:12] <slickymasterWork> because if it's that section, what I'm getting is Mousepad, not Abiword
[18:12] <elfy> and I'm not looking right now - time for food approacheth
[18:12] <slickymasterWork> my doubt is if whether I should comment it on his report, or not
[18:15] <elfy> comment all you want :)
[18:15] <elfy> make sure to read the 4500 word bug reporting wiki first though :D
[18:15] <slickymasterWork> lol
[18:15] <slickymasterWork> so, in your opinion it's the same bug?
[18:16] <slickymasterWork> only a slight variation 
[18:17] <elfy> slickymasterWork: I don't know - I've not had time to look yet :)
[18:17] <slickymasterWork> ok, I'll comment on his report
[18:41] <slickymasterWork> knome, your intended fiddling on the ubiquity slideshow will just cover the artwork, right?
[18:42] <knome> slickymasterWork, there's another work item for the content if you look really closely :)
[18:42] <slickymasterWork> hmmm, now I see it
[18:43] <slickymasterWork> you go out of your way to keep me busy :P
[18:44] <knome> ;)
[18:46]  * slickymasterWork resolves to reciprocate to knome remembering him about the stats of the finnish -docs translation, 96%
[18:47] <knome> since you're going to mess it up before the end of the cycle anyway, i'll just leave it at 96% for now just to tease you ;)
[18:48] <slickymasterWork> lmao
[20:10] <elfy> http://status.ubuntu.com/ubuntu-v/group/topic-v-flavor-xubuntu.html
[20:18] <knome> nice :)
[20:32] <elfy> slickymaster: I've confirmed jjfrv8's mimetype bug
[20:40] <ochosi> http://status.ubuntu.com/ubuntu-v/group/topic-v-flavor-xubuntu.html
[20:40] <ochosi> oh, elfy already pasted it :)
[20:40] <knome> haha:)
[20:40] <knome> hello ochosi 
[20:40] <Unit193> Still very much on screen too. :P
[20:40] <ochosi> we're pretty much on track for the moment
[20:40] <ochosi> hey knome 
[20:40] <knome> of course we are, the tracking started today, so everything that is done before today isn't even counted
[20:41]  * ochosi votes for restarting the tracker on a daily basis
[20:42] <knome> hah
[20:45]  * elfy votes for turning them off :)
[20:45] <ochosi> elfy: indicators still broken in V?
[20:46] <elfy> not seen a recent repetition ochosi 
[20:47] <ochosi> you mean they're working again?
[20:47] <elfy> it's on my radar - I will say if I see it
[20:47] <elfy> still get odd gtk2ish qt for a short while - changing desktop back and forth resets that for some reason
[20:47] <ochosi> hm, odd
[20:48] <ochosi> well good if the indicators load again
[20:48] <ochosi> at least for now
[20:48] <ochosi> guess we have to test the qt thing more
[20:48] <knome> elfy, i know you're seeing it, but for the record, #ubuntu-quality (and for slickymaster too)
[20:48] <elfy> indicators work 
[20:49] <elfy> iirc I got some updates after seeing it the last time
[20:49] <ochosi> ok
[20:49] <elfy> knome: ack
[20:49] <ochosi> was just wondering since it was still on the bugs-blueprint and all
[20:50] <elfy> ochosi: well re qt - I can more or less constantly test any fixes re that - clementine is on all the time pc is on
[20:51] <ochosi> do you test other qt apps than clementine too?
[20:51] <ochosi> just to make sure this isn't another xchat scenario :>
[20:51] <elfy> ochosi: well - we can remove it if we need - but it's not hurting anything by being there imo
[20:52] <elfy> not as a rule
[20:52] <elfy> got something I could use :D
[20:52] <ochosi> sure, let's leave it on there for now
[20:52] <ochosi> no rush
[20:53] <elfy> oh yea - that's the bug someone else marked as a dupe 
[20:53] <elfy> of a Private one
[20:59] <ochosi> humm, quick question
[21:00] <ochosi> is the ubuntu software center really up for discussion?
[21:00] <ochosi> (i just noticed it on the features blueprint right now for the first time)
[21:00] <elfy> no idea?
[21:01] <elfy> not seen anything about that - other than a general thing the other day
[21:02] <ochosi> yeah, that mailinglist-discussion isn't a valid basis for a workitem imo
[21:02] <ochosi> otherwise we'd have libreoffice on there 
[21:02] <ochosi> *every* cycle
[21:02] <elfy> isn't lo on there?
[21:03] <elfy> :p
[21:04] <ochosi> meh, why don't blueprints have a history...
[21:05] <ochosi> skellat: just curious, did you add the workitem for reviewing USC?
[21:05] <elfy> talking of discussions - dkessel if you decide to do anything re deja-dup I did some screenies of it and grsync and some memory figures and the extra packages installed
[21:05] <elfy> ochosi: blueprint history is on mailing list - not easy though
[21:08] <elfy> and yes it was skellat 28/10 
[21:09] <ochosi> k, thanks elfy
[21:11] <elfy> ftr even though I don't use it myself - I see no real reason to go backwards
[21:11] <ochosi> go backwards on what?
[21:11] <ochosi> USC?
[21:11] <elfy> yea
[21:11] <ochosi> skellat: ok, now that we've cleared that, may i ask why you added the workitem exactly?
[21:12] <ochosi> elfy: yeah, me neither. and that ML discussion didn't suggest it'd make any sense tbh
[21:12] <elfy> yep
[21:12] <knome> i don't use USC either, but i don't think removing that and bringing synaptic back is the right thing either
[21:14] <elfy> I install synaptic - but mostly because I'm too lazy to be worrying about removing the wrong kernels in terminal :)
[21:14] <knome> i just remove USC and use apt-get
[21:14] <knome> elfy, apt-get --purge autoremove :)
[21:15] <elfy> I don't remove it - I check now again that it *works* 
[21:15] <knome> ;)
[21:18] <elfy> no idea why I bother tbh - I guess ubuntu check it somewhere :)
[21:18] <ochosi> one would hope so
[21:18] <elfy> so - back to qt - no idea what qt apps I could use to check it's not just clementine failing 
[21:18] <elfy> and no I'm not using vlc 
[21:19] <elfy> heh
[21:19] <elfy> or should that be "one would hope not" 
[21:31] <Unit193> elfy: "I'm too lazy to be worrying about removing the wrong kernels" You hit the wrong one, it tells you it's the running kernel and asks you to confirm removal, fwiw.
[21:32] <Unit193> Skype is Qt too, but that won't help either...
[21:32] <elfy> so I'd have to do it twice - notice the lazy bit :)
[21:34] <elfy> :)
[21:35] <slickymaster> elfy, thing is that I'm not excatly seeing what you both see
[21:37] <ochosi> elfy: yeah, i'm not using many qt apps either
[21:37] <ochosi> and skype is really a bad example
[21:41] <elfy> slickymaster: mmm - well 2 out of 3 do - this is when you change properties in thunar, then re-open mime editor
[21:41] <elfy> ochosi: yea - not sure where to go with it tbh, I don't see many other's mentioning it - the bug where it showed up was the first time I'd seen it elsewhere
[21:42] <slickymaster> yes, like I commented https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1391184/comments/3
[21:44] <elfy> mmm
[21:45] <elfy> I think something is being lost in translation here 
[21:45] <elfy> or we're talking about 2 seperate things
[21:46] <slickymaster> I think we're might be talking about 2 seperate things
[21:47] <elfy> if you change to abiword in mime editor - it sets field as user set, if you change in thunar it leaves it as default even though it says abiword
[21:47] <elfy> but if you change it without closing mime editor - it doesn't change in real time
[21:47] <elfy> one bit of the testcase works ok - the other doesn't 
[21:47] <slickymaster> tbh I don't remember now whether I close it or not
[21:47] <slickymaster> but I can do it again tomorrow
[21:48] <slickymaster> yeah, the second section of it doesn't
[22:44] <brainwash> ochosi: I was just wondering, why this report is still open
[22:44] <brainwash> bug 1325228
[22:44] <brainwash> it cannot be fixed
[22:45] <brainwash> at least not in the code of the current light-locker
[22:45] <knome> because somebody reopened it
[22:45] <knome> brainwash, if you read the bug comments, you'd notice that it had been "expired"
[22:45] <brainwash> yes, soft closed
[22:46] <brainwash> won't fix or invalid
[22:47] <knome> even if it was one of those, anybody could open it
[22:48] <knome> it's invalid now
[22:48] <brainwash> you cannot change won't fix
[22:48] <brainwash> ok, thanks
[22:49] <knome> you can always file a new bug then, which is even more annoying..
[22:51] <brainwash> why would they file a new bug report? they can just add a comment to the exiting one
[22:52] <knome> because they feel wrongdoed since the bug is marked "wontfix"
[22:52] <knome> it's not a rational thing they are doing.
[22:53] <brainwash> hopefully they manage to file the new report against the correct package then
[22:54] <knome> just affecting the right package in the same bug would do
[22:54] <knome> and no, i don't think they manage to do that
[22:54] <knome> once somebody has said it's a bug in A, they will insist that it's a bug in A until it's fixed in B, after which they don't care
[22:55] <Unit193> http://xubuntu.org/news/screen-locking-in-xubuntu-14-04/ says to do one thing he did, "Add your user to the “audio” group on your computer and  music playback will continue also with light-locker"  (and yes, that double space wasn't added by me.)
[22:55] <knome> stop the press! there's a double space in the website!
[23:00] <brainwash> light-locker caused much trouble, but it works fine for the majority of xubuntu users I'd guess
[23:03] <brainwash> knome: bug 1307929 any news?