[06:14] <flocculant> Unit193: I did that for you
[06:15] <Unit193> \o/
[06:15] <flocculant> mostly because you can do all that packagy stuff but not edit a wiki page :p
[06:15] <Unit193> Wikis are hard, or at least logging in is. :3
[06:15] <flocculant> I think  they might have looked at that
[06:16] <flocculant> whilst coming up with all ways to make it harder :p
[06:17] <flocculant> not really sure milestones needs to be there - given that qa and tech lead and web lead say no to b1 and no-one else cares enough to comment
[06:17] <flocculant> and I'll always -1 any raspberry pi thing officially 
[06:17] <flocculant> so can just wait for the workhorse ping :p
[07:31] <flocculant> bluesabre: re thunar and testing - been thinking about this - not sure quite what we can do with the current testcase - other than ask people to sit there copy/pasting till they see problems - then how long do we ask them to do it for ;)
[07:32] <flocculant> or we could add a very specific testcase - sit there copy/pasting > how long did it take to crash on you? 
[07:32] <flocculant> did it crash quicker post-crash? 
[07:32] <flocculant> or: did you give up and use a different file manager :p
[08:33] <Unit193> ochosi: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1576576
[10:40] <bluesabre> flocculant: if the gui automation (whats that called again) worked with gtk2, we could easily make a script to test it
[10:56] <flocculant> yea  - but it doesn't :p
[11:09] <flocculant> and I've given up thinking about it tbh ;)
[11:16] <flocculant> knome: when you've got 10 minutes or so and it's not lunch time can we haz chat about buildlog and tracker thingymajig :)
[11:33] <bluesabre> flocculant: I'll figure something out
[12:53] <knome> flocculant, i'll be on and off today, but feel free to talk about something and i'll reply when i'm back ;)
[17:55] <flocculant> knome: no rush - really don't want a disjointed discussion
[18:21] <flocculant> knome: added some about this to very top of http://pad.ubuntu.com/xubuntuqa-y-cycle
[18:46] <Unit193> ochosi: In case you didn't see, there was also "interesting" discussions with that link to the bug.
[18:46] <flocculant> tried hard not to ramble too much
[18:47] <flocculant> Unit193: in -desktop or on bug? 
[18:47] <Unit193> -devel, actually.
[18:47] <flocculant> oh right - well that just seems really pointless for me to idle in :)
[18:48] <ochosi> Unit193: uhm when what where?
[18:48] <ochosi> (sry, i vaguely remember you posting a link to a gtk3.20 lp bug today but i was too busy @work to read9
[18:49] <Unit193> ochosi: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1576576 I linked to this, there was discussion in -devel at 04:21 local time.
[18:49] <flocculant> evening ochosi :)
[18:49] <Unit193> Basically a GNOME guy and unity peeps talking about if they're going to update this cycle.
[18:49] <ochosi> right
[18:49] <ochosi> well no worries i'll work on the greybird rewrite soon
[18:50] <ochosi> so we'll be good either way
[18:50] <ochosi> the only thing that could bite us is if xfce applications inject css
[18:50] <ochosi> cause that will fail
[18:50] <Unit193> Unity wasn't so interested in updating gtk3, actually.  It was interesting, they have nobody at all that really understands themes now. :P
[18:50] <ochosi> or: will need patches for 3.20 compat
[18:50] <ochosi> yeah, i know. i talked to larsu at fosdem before he left the desktop team and canonical altogether
[18:51] <ochosi> basically they'll have to switch to adwaita soon if they don't find anyone who maintains their themes
[18:51] <ochosi> would have to be a community member from what i see
[18:52] <Unit193> Oh?  Wow, that's lovely.
[18:52] <flocculant> mmm
[18:52] <Unit193> ochosi: Know if satya will be working on Numix? :P
[18:52] <ochosi> i think they're already working on it
[18:53] <ochosi> so numix should be good i guess
[18:53] <Unit193> Eric seems to have taken an interest in Blackbird, no?
[19:35] <Unit193> menulibre 2.0.7-1.1 uploaded by Samuel Henrique Oltramari Pinto (SamuelOPH) (Closes: #811324)
[19:38] <nairwolf> Hi guys (and specially flocculant), can you look this bug and see if you are able to reproduce it, please ? https://bugs.launchpad.net/ubuntu/+source/xfce4-appfinder/+bug/1576771
[19:38] <pleia2> flocculant: g+ and fb done re: irc sessions
[19:38] <pleia2> I'll try to keep an eye on it to see if people yay in those places ;)
[19:39] <flocculant> pleia2: thanks :)
[19:40] <flocculant> I think I see fb stuff - but maybe not
[19:40] <flocculant> pleia2: re  counting - I'll probably ask for a bump in a week or so - then see what 'yay's' we had - then follow up
[19:41] <flocculant> I will follow up with either a 'nope then' or more detail 
[19:41] <pleia2> okie
[19:43] <flocculant> pleia2: freudian almost  ... "but you're welcome to follow this path. Since our team handling the official social media is very small[0"
[19:43] <flocculant> :)
[19:44] <flocculant> nairwolf: I saw that bug - not looked in detail yet - will try tomorrow if I get chance
[19:44] <nairwolf> ok, so we'll talk to that tomorrow if I can be here also. (Should be outstide this saturday)
[19:45] <nairwolf> dinner time, see you. 
[21:09] <knome> flocculant, we probably want to just look at the source (not LP) for the builds, should be relatively simple to fetch that data
[21:10] <flocculant> mmk 
[21:16] <nairwolf> knome: which sources ? 
[21:16] <knome> nairwolf, build log
[21:18] <knome> flocculant, also left a comment on the pad
[21:20] <nairwolf> oh, ok
[21:21] <knome> nairwolf, if you are very interested in *any* discussions happening on this channel, i'd suggest you to either 1) get a shell so you can get a bnc/client always stay on the channel so you can check the backlog 2) start reading the logs found from irclogs.ubuntu.com
[21:28] <nairwolf> knome: Usually, I'm reading logs at irclogs.ubuntu.com, but this time, I didn't
[21:32] <flocculant> knome: yea - thought second might be better
[21:34] <flocculant> re multiple builds - they're only likely to happen when milestone - or someone from release team triggers a rebuild
[21:34] <knome> yeah, but the tracker doesn't know when that happens
[21:34] <flocculant> s/likely/going to afaik
[21:34] <flocculant> nope
[21:34] <flocculant> all tracker knows is date.1
[21:34] <knome> so it needs to check a possible .1/.x rebuild every time
[21:34] <knome> indeed
[21:34] <flocculant> or shows
[21:34] <knome> the tracker i'm referring to here is dev.xubuntu.org
[21:35] <flocculant> oh
[21:35] <knome> but sure, the iso tracker too
[21:35] <flocculant> well I'm referring to what shows on iso
[21:35] <knome> mhm
[21:35] <flocculant> all that aside
[21:35] <flocculant> in fact - we 'could' end up in the same position as we would get from autotest
[21:36] <flocculant> eg build builds - build lands on iso tracker - dev tracker says 'yay'
[21:36] <flocculant> but it doesn't actually work
[21:37] <flocculant> the only way to get around that is Last options thinking: 
[21:37] <knome> well, i was thinking about something like asking http headers to see if a file exists
[21:37] <flocculant> if that's possible 
[21:37] <flocculant> from iso.tracker? 
[21:38] <bluesabre> evening alllll
[21:38] <knome> ugh, no, i most likely won't touch the ISO tracker :P
[21:38] <knome> but i can talk to matthew in SF in june...
[21:38] <flocculant> knome: mmm
[21:39] <flocculant> who's matthew? 
[21:39] <flocculant> bluesabre: evening :)
[21:39] <knome> MatthewAllen, from code-in
[21:39] <knome> didn't he poke the tracker too?
[21:39] <bluesabre> hey flocculant knome
[21:39] <flocculant> knome: well - a positive from the image test on the tracker is the only real positive
[21:39] <knome> 'lo bluesabre 
[21:39] <flocculant> all the others are positives that we have a build
[21:40] <knome> yep
[21:40] <flocculant> and if the build includes a broken ubiquity ... 
[21:40] <knome> ;)=
[21:40] <Unit193> bluesabre: /lastlog menulibre, just an FYI.
[21:40] <flocculant> knome: if it's possible to do - the iso tracker would be my preference unfortunately :p
[21:41] <flocculant> assuming we can move cron time of build
[21:41] <knome> flocculant, ack
[21:41] <knome> let's see
[21:41] <flocculant> ok 
[21:41] <knome> i need to think this with no smudge on the brain :P
[21:41] <flocculant> anyway - I think we're both up to speed on the 'what' at least :)
[21:41] <knome> and by smudge i mean snot
[21:41] <flocculant> :(
[21:41] <flocculant> still full of it then 
[21:42] <flocculant> :p
[21:42] <knome> well, kind of the aftermath
[21:42] <knome> didn't have much of it coming out when i was "really" sick
[21:42] <flocculant> almost worst
[21:42] <knome> yep
[21:42] <flocculant> yea - pretty normal state of affairs in my experience 
[21:42] <knome> but that happens, so...
[21:42] <flocculant> :)
[21:43] <flocculant> bluesabre: so good luck with gtk2 and autotest :p
[22:21] <bluesabre> flocculant: probably going to look at other options
[22:25] <nairwolf> I think I've discovered a bug on Mousepad. 
[22:26] <nairwolf> Open mousepad, write some stupid thoughts, then do alt+f4 and click on "Do not save" it's not highlighted as other options
[22:26] <nairwolf> no, do not click on "do not save", but move the cursor with the keyboard to "do not save"
[22:27] <nairwolf> Do you see this bug ? 
[22:28] <bluesabre> I do see that bug
[22:29] <bluesabre> feel free to report it :)
[22:29] <nairwolf> ok
[22:34] <nairwolf> Done : https://bugs.launchpad.net/ubuntu/+source/mousepad/+bug/1576890
[22:34] <nairwolf> As I'm not an native english speaker tell me if something isn't clear
[22:34] <nairwolf> I will edit my description
[22:35] <bluesabre> I'd say that it's not highlighted in the same way the other buttons are
[22:36] <nairwolf> It's a graphical issue, so it seems hard for me to solve this bug. But, I'll try to see what I can do
[22:36] <nairwolf> Next week, I will be in holydays, so I should start to work the next week
[22:37] <nairwolf> ok, thanks
[22:38] <nairwolf> I've edited the bug report
[22:38] <nairwolf> Now, it's time to go to bed. See you bluesabre ;)