[00:02] <ali1234> this whole thing is one big circular reference
[00:26] <ali1234> right, finally it's fixed
[00:26] <ali1234> http://bug-attachment.xfce.org/attachment.cgi?id=5747
[09:58] <elfy> ochosi: not sure if this is expected or not, can you see where to enable an item here - http://www.zimagez.com/zimage/screenshot-121114-095725.php
[09:59] <elfy> you have to guess - http://www.zimagez.com/zimage/screenshot-121114-095752.php
[10:01] <dkessel> lol elfy :)
[10:01] <elfy> see the same in synaptic - so it's not just transmission
[10:01] <dkessel> sure, why not there? it is obvious :)
[10:01] <elfy> hey dkessel - good morning to you 
[10:02] <dkessel> hey elfy
[10:02] <dkessel> good morning to you too :)
[10:02] <dkessel> i mean, it has been there the previous versions... ;) just kidding
[10:07] <elfy> possibly - the last cycle I took a lot of notice was 14.04
[11:01] <elfy> slickymasterWork: I looked at the task manager testcase - bug 1391636
[11:01] <elfy> just needs checking over and I'll get on and deal with it
[11:02] <elfy> or dkessel even - anyone in -qa :)
[11:03] <slickymasterWork> I can make a MP tonight if you want me to, elfy
[11:03] <elfy> I can do it - not working this week
[11:04] <slickymasterWork> s/it/if
[11:05] <slickymasterWork> ok, I can review it if you want
[11:05] <elfy> ta :)
[11:05] <slickymasterWork> the bug description pretty much sums it all elfy 
[11:12] <elfy> :)
[12:45] <dkessel> bluesabre: looks like I can just use the "BuilderName" property of the widgets to identify them in autopilot. I guess there is no need to give everything an ID then - as long as the "BuilderName" does not change
[12:51]  * dkessel feels so stupid
[12:51] <dkessel> I should have seen that converting the manual catfish test requires the adminstrator password... I don't think this will work
[12:54] <elfy> dkessel: mmm 
[12:54] <dkessel> i can build it... but it won't work without the correct password
[12:54] <elfy> dkessel: you're directly converting manual to auto? 
[12:55] <dkessel> elfy: yes
[12:55] <elfy> I'll just pull up the manual one 
[12:57] <elfy> dkessel: so why not get it to search for files that are just always going to be there regardless instead of creating some then updating db
[12:59] <dkessel> elfy: sure, why not.
[12:59] <elfy> the only issue then would be being unable to check case sensitivity 
[12:59] <dkessel> but it takes away some of the test's value
[12:59] <dkessel> i'll ask in the autopilot channel if they have an idea
[13:00] <elfy> ok
[13:57] <jjfrv8> elfy, I posted a comment on bug 1391636
[13:57] <jjfrv8> elfy, did you see bug 1391357 yet?
[14:02] <jjfrv8> I did not include the suggested revisions in that one ^^ like you did in yours. I was going to ask if you wanted me to draft an MP.
[14:10] <elfy> jjfrv8: go ahead :)
[14:10] <elfy> and no I'd not seen that bug
[14:12] <elfy> jjfrv8: thanks for comment in the task manager one
[14:18] <jjfrv8> ok, will do.
[14:24] <slickymasterWork> hey jjfrv8 did you get anywhere with http://irclogs.ubuntu.com/2014/10/29/%23xubuntu-devel.html#t12:11
[14:27] <jjfrv8> slickymasterWork, I figured that was a dead issue. The vote seemed to be that things were okay as they were.
[14:31] <ochosi> elfy: that is a "bug" in our gtk themes (yeah, gtk devs decided to change some theming properties' names again in 3.14) which is already taken care of in git
[14:32] <ochosi> i suppose you're not using the shimmer-daily PPA for themes? if not, no worries, i guess we can arrange an update of the themes packages for V soonish
[14:32] <ochosi> (but just so you know it should already be taken care of. and thanks for noticing/notifying)
[14:33] <elfy> ochosi: thanks - and yes I have -staging and shimmer ppa's 
[14:33] <ochosi> hmm, odd. let me check when that last built...
[14:33] <elfy> no need for a pointless bug report then - that's good :)
[14:34] <elfy> I got shimmer updates a day or so ago iirc
[14:34] <ochosi> humm, supposedly it should be fixed in the last build, so that's odd
[14:34] <ochosi> aaaaah, ofc
[14:34] <ochosi> you're still having gtk3.12
[14:34] <ochosi> and the themes are already prepped for 3.14
[14:34] <ochosi> so you get the regression you'd get without the patch in 3.14 in 3.12 :>
[14:35] <ochosi> so i guess i was "too fast" there
[14:35] <ochosi> as soon as 3.14 lands, things should be back to normal
[14:35] <elfy> ok - cool, as long as there is a reason - I can just wait for 3.14 and watch in wonder as all is fixed as if by magic then :)
[14:35] <ochosi> indeed
[14:36] <elfy> if it's March and we've not for gtk3.14 I will let you know you need to reverse course :D
[14:37] <ochosi> yup, good to keep that on the radar :]
[14:37] <ochosi> but i suppose this time 3.14 is bound to land
[14:37] <ochosi> i saw some folks in -desktop messing with patches for it already
[14:37] <elfy> he he he 
[14:42] <slickymasterWork> jjfrv8, well it wasn't a proper vote. If on one hand ochosi doesn't really have any strong on dropping the icon from whisker, on the other knome thinks that it's better to keep it and solve the ambiguity docs-internally
[14:42] <slickymasterWork> and no one else in -team besides them had reaaly pronounce on the subject
[14:42] <slickymasterWork> s/reaaly/really 
[14:44] <ochosi> slickymasterWork: you can also ask around at tomorrow's meeting
[14:44] <ochosi> can't promise yet i'll make it, i'm travelling abroad again
[14:45] <ochosi> but as i have no strong opinion, it probably doesn't matter too much
[14:45] <slickymasterWork> I think all add it to the meeting agenda
[14:47] <Unit193> I can that I'll miss.
[14:48] <slickymasterWork> buuu
[15:01] <jjfrv8> slickymasterWork, I won't be able to make the meeting. My proxy would be to abstain. If you decide to proceed with something, I don't think I would be a good candidate to work on it.
[15:01] <jjfrv8> I'd probably end up adding confusion to something that other folks don't really see as an issue in the first place.
[15:02] <Unit193> ochosi: If you want to track more gst0.10 bugs, https://github.com/squentin/gmusicbrowser/issues/76
[15:02] <jjfrv8> bbl
[15:02] <elfy> personally - removing something from the menu because docs look wrong is not the right way to do things
[15:03] <knome> necessarily
[15:03] <elfy> wut?
[15:03] <elfy> why is Unit193 posting one word comments as knome :p
[15:03] <knome> it's not necessarily wrong
[15:04] <knome> i mean...
[15:04] <elfy> I know what you mean :)
[15:04] <knome> doing it for that sake is wrong, but the action itself is not necessarily wrong :P
[15:04] <elfy> yep
[15:04] <knome> i don't have a strong opinion on this
[15:05] <knome> the only argument i have for keeping what we have is that some users have learned this way
[15:05] <knome> we don't want to mess that up now
[15:05] <elfy> yep - that would be my position
[15:05] <knome> whether that'd balance out with new users not having at all ambiguity is a different thing
[15:06] <elfy> well 
[15:07] <elfy> most people would look at what they see -> docs if they can't find something
[15:07] <elfy> in my experience
[15:07] <knome> mhm
[15:07] <Unit193> Or when we tell them to.
[15:16] <slickymasterWork> ok, got it jjfrv8. Thanks for the feedback
[19:19] <Noskcaj> elfy, ochosi: gtk 3.14's blocker list is at http://pad.ubuntu.com/gtk-update-v if you're wondering what we're waiting for
[20:20] <brainwash> bluesabre: there is a patch attached to bug 1211933
[20:21] <brainwash> for xubuntu-live-settings
[20:22] <brainwash> should we apply this patch? or close the report as won't fix?
[23:54] <skellat> brainwash: I'll say WON'TFIX as this appears unrelated to the original bug -- https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1211933/comments/8