[05:03] <didrocks> good morning
[07:03] <seb128> good morning desktopers!
[07:05] <didrocks> re seb128
[07:05] <seb128> re didrocks :-)
[07:15] <seb128> Laney, there is a grumpy user on bug #1447224 having issues with the update, can you check if those are regression from the sru update?
[08:03] <willcooke> morning
[08:03] <Laney> hello
[08:03] <Laney> seb128: see regression potential in the report
[08:04] <didrocks> hey willcooke, Laney!
[08:05] <seb128> Laney, hey, oh I see, is that an unity issue? why can't gmenu based menus be used while old style ones work?
[08:07] <seb128> hey willcooke
[08:07] <seb128> Laney, had a good w.e?
[08:12] <Sweet5hark> moin
[08:12] <Sweet5hark> TIL you can troll reddit into a few thousand blog views by bikeshedding about C++ idoms ...
[08:12] <seb128> hey Sweet5hark
[08:12] <didrocks> good morning Sweet5hark
[08:12] <Sweet5hark> Bonjour, seb128!
[08:12] <Sweet5hark> et didrocks!
[08:12] <seb128> Sweet5hark, is that what you did this w.e? ;-)
[08:13] <RAOF> Hm, no pitti? On holiday no doubt, the dastard!
[08:13] <Sweet5hark> seb128: yes: https://skyfromme.wordpress.com/2015/07/18/blast-from-the-past-the-pimpl/
[08:13] <RAOF> Also, hello seb128, didrocks, Sweet5hark and everyone!
[08:13] <seb128> RAOF, he is, indeed!
[08:14] <seb128> RAOF, hey
[08:14] <Sweet5hark> seb128: well, and buying a new amp as my old one broke. The new amp then needed "testing".
[08:14]  * RAOF is no longer on holiday :)
[08:14] <didrocks> good evening RAOF ;)
[08:14] <Laney> seb128: http://irclogs.ubuntu.com/2015/06/05/%23ubuntu-desktop.html#t10:17
[08:14] <Laney> yes, fine weekend thanks, wedding then hanging out with family
[08:14] <Laney> hey didrocks!!!!!!!
[08:16] <seb128> Laney, thanks for log, and I agree on the "fair enough"
[08:16] <seb128> can you maybe comment on the bug still so the grumpy user doesn't become even grumpied?
[08:16] <seb128> r
[08:18] <Laney> haha, if only commenting will have that effect
[08:18] <Laney> but yes
[08:19] <Laney> thx for fixing gtk btw
[08:19] <Laney> new mir seems to have knackered boot tests
[08:19] <Laney> anpok: have you seen that?
[08:22] <anpok> Laney: that was on thursday to friday night I think..
[08:23] <anpok> i forgot to add the url-dispatcher MP to the spread sheet..
[08:23] <Laney> hmm?
[08:24] <anpok> url-dispatcher is another mirclient user
[08:24] <Laney> anpok: will that fix the boottest failure?
[08:24] <anpok> i am not sure if the rebuilt url-dispatcher is in proposed yet
[08:25] <Laney> https://launchpad.net/ubuntu/+source/url-dispatcher/0.1+15.10.20150717-0ubuntu1 this is
[08:26] <anpok> oh that happened already on friday
[08:27] <seb128> Laney, yw for gtk, thanks to pitti for finding it through some testing infra (I think)
[08:27] <seb128> Laney, the bootest thing was discussed a bit on friday yes, people were not able to reproduce and the test provide almost no detail
[08:27] <seb128> unsure if they came to any conclusion
[08:28] <Laney> bleh
[08:28] <Laney> I just see a timeout error
[08:28] <seb128> right, like the dash was not coming up
[08:29] <Laney> it should attach logs really
[08:29] <Laney> would file a bug if I knew which ones would be useful
[08:29] <Laney> .cache/upstart/* and ...?
[08:29] <anpok> would boottest attempt to uninstall older package provided by an older mir release?
[08:30] <anpok> lightdm and unity-system-compositor logs .. probably
[08:30] <anpok>  /var/log/lightdm/*
[08:31] <anpok> i mean if it attempts to uninstall those provided by the old mir release it would remove all clients
[08:31] <anpok> or libraries depending on clients..
[08:31] <Laney> I don't think so
[08:31] <Laney> https://jenkins.qa.ubuntu.com/job/wily-boottest-mir/lastBuild/artifact/results/log/*view*/
[08:34] <seb128> that log is weird
[08:35] <seb128> the silo/mir update includes more component than those updated
[08:35] <seb128> like platform-api rebuilds
[08:35] <seb128> unsure if the issue is that those are missing
[08:41] <Laney> it didn't update the whole transition
[08:41] <Laney> just that one package I guess
[08:41] <seb128> yeah
[08:41] <Laney> would that break things?
[08:41] <seb128> there might miss conflicts or such
[08:41] <seb128> no idea
[08:41] <seb128> unsure if anyone tested it out of the silo
[08:41] <seb128> in partial upgrade scenarios
[08:41] <Laney> lemme dig out the phone and charge it up
[08:42] <seb128> I tested the mir update on friday
[08:42] <seb128> but that was full silo set
[08:42] <seb128> let me see if I can downgrade bits
[08:42] <Laney> I was going to run the boottest locally
[08:42] <Laney> assuming that is possible
[08:44] <seb128> dunno if that's possible, if you figure it out let me know how, that can be useful
[08:45] <seb128> bah, n7 went flat over the w.e, of course
[08:46] <Laney> will need a while to charge it up too
[08:46] <Laney> haven't used for ages
[08:47] <Laney> seb128: anpok: https://bugs.launchpad.net/ubuntu-test-cases/+bug/1476153
[08:47] <seb128> Laney, thanks
[08:49] <Laney> dunno if that is the right project
[08:57] <anpok> seb128, Laney: can we rerun wily-boottest-mir?
[08:58] <seb128> some people did on friday I think
[08:58] <seb128> it's also failing for the different components involved in that transition, not only on one
[08:59] <anpok> but that was before the url-dispatcher landing?
[08:59] <seb128> that doesn't matter
[08:59] <seb128> url-dispatcher not build rebuilt wouldn't prevent unity8 to start
[09:02] <anpok> i agree because it was no problem during testing
[09:20] <seb128> Laney, anpok, k, I can reproduce the issue easily
[09:20] <seb128> I just downgraded unity-system-compositor
[09:20] <seb128> that's not updated on https://jenkins.qa.ubuntu.com/job/wily-boottest-mir/lastBuild/artifact/results/log/*view*/
[09:22] <seb128> if you get u-s-c built with old mir and update mir u-s-c hits a a stack smash error
[09:22] <Laney> nice
[09:22] <Laney> some Breaks needed then I guess
[09:22] <seb128> indeed
[09:23] <seb128> updating u-s-c, restart lightdm and things work
[09:24] <Laney> want to manually upload it to see if it fixes boottest?
[09:25] <seb128> unsure
[09:25] <seb128> I would prefer for the mir team to fix it as want/commit the fix at the proper place
[09:25] <seb128> I mentioned it on  #ci-eng as well
[09:26] <Laney> bleh, this always takes ages
[09:26] <Laney> but as you wish
[09:26] <seb128> also I'm unsure if mir <-> u-s-c is the issue
[09:26] <seb128> or if we should only have one libmirclient<n> installed
[09:26] <seb128> that needs to match the server
[09:27] <seb128> Laney, well, feel free to do the change/upload if you want, I'm not going to stop you or complain ;-)
[09:28] <seb128> I'm just not sure enough of what's the right change/prefer to wait a bit for mir team the ping back with what they want to be done
[09:28] <Laney> ok, we can do that
[09:44] <RAOF> Urgh. We've gone to some lengths to ensure multiple libmirclient should be usable in parallel :(
[09:45] <chrisccoulson> ricotz, you asked about thunderbird 38.1.0 on friday - I've just opened bug 1476169
[09:49] <chrisccoulson> ricotz, also, thanks for uploading the new Firefox beta. Would you mind updating the bzr branches though? :)
[09:54] <ricotz> chrisccoulson, ah nice ;)
[09:56] <ricotz> chrisccoulson, I didnt bother to push changelog-only change, and those branches could use some updates e.g. update bzr-format and sync them a bit to reduce the diff
[09:57] <ricotz> (so I don't want to mess with them)
[10:01] <anpok> seb128: why is u-s-c not updated with wily-boottest-mir?
[10:02] <anpok> hm the boottest also keeps qtmir
[10:04] <anpok> ah .. ok i guess I misunderstood what boottest does..
[12:02] <seb128> RAOF, well, what bit changed in a incompatible way making u-s-c not start?
[12:02] <seb128> anpok, bootest seems to do "take $current_distro, install $update, check the system boots"
[12:03] <seb128> so to test the mir update, it installs only mir
[12:08] <anpok> seb128: the problem seems to be that with the update we load mircommon and mirplatform from both 0.14 and 0.13.3.. I believe we could resolve that by bumping the version number of the android server platofmr package.. but I am not sure if that would cover all cases. still looking where the actual failure happens
[12:09] <seb128> anpok, you could use package depends/conflicts/... etc to make sure that new mir uninstall old u-s-c
[12:09] <seb128> but I'm unsure the issue is specific to u-s-c
[12:09] <seb128> if it's wrong to have 2 versions of mircommon/mirplatform loaded, maybe then those libs should conflict
[12:10] <Laney> RAOF said it is supposed to work
[12:11] <anpok> yes it ought to work .. kind of (as in we do not have an acceptance test that proves it).. the failure happens during the first client connect..
[12:11] <seb128> Laney, yeah, so maybe the right fix is a mir code fix
[12:11] <seb128> and not forcing u-s-c the be updated with mir
[12:11]  * Laney nods
[12:11] <Laney> good that it found a real bug
[12:12] <seb128> :-)
[12:12] <seb128> unsure what to do next
[12:12] <seb128> that might not be worth holding the update, in practice it impacts only partial upgrades
[12:12]  * anpok currently looks into debugging the issue.. 
[12:12] <anpok> but we could also take a short cut and mark the versions conflicting..
[12:13] <anpok> or even that
[12:13] <seb128> right, that's probably good enough to unblock that migration, shouldn't be used as a reason to not investigate the issue though
[13:48] <Sweet5hark> ugh. after trolling reddit over the weekend, now someone posted this to hacker news ...
[14:03] <willcooke> Sweet5hark, dont leave us hanging :)
[14:05] <Sweet5hark> willcooke: oh just my pointless bikeshedding rant on C++ coding style: https://news.ycombinator.com/item?id=9915841
[14:06] <willcooke> :)
[14:38] <balloons> ack
[15:47] <seb128> Laney, unsure if you are following that totem sru bug, one user claims the update make the rotation item stop working, I asked him to open a new bug report about that, it works on wily but I don't have a vivid system handy to test the SRU (can do in a vm if you want though)
[15:53] <Laney> yes I am subscribed, I will try later
[16:06] <Laney> http://people.canonical.com/~laney/weird-things/rotate.png works
[16:06] <Laney> ignore the corruption
[16:08] <seb128> Laney, good :-)
[16:09] <seb128> you also get that font corruption issue then?
[16:09] <seb128> it's an annoying one :-/
[16:14] <Laney> seb128: seems bug #1261916
[16:14] <Laney> patch to disable composite something is linked there by mlankhorst
[16:14] <seb128> oh ok, not the same then
[16:14] <Laney> no?
[16:14] <seb128> it happens sometime on my real system with the intel driver
[16:15] <Laney> oh right, no I never see it there
[16:15] <seb128> https://bugs.freedesktop.org/show_bug.cgi?id=88584
[16:19] <Laney> haha
[16:19] <Laney> http://pkgs.fedoraproject.org/cgit/xorg-x11-drv-qxl.git/tree/0001-worst-hack-of-all-time-to-qxl-driver.patch
[16:25] <seb128> hack!
[16:42]  * Laney sees that charles left us :(
[16:49] <willcooke> ?!
[16:49] <Laney> !!! just this channel
[16:49] <Laney> be calm
[16:49] <Laney> you too ubot5
[16:49] <willcooke> heh
[16:50] <willcooke> laney and ubot5 are like two little Fonzys
[16:52] <davmor2> willcooke: surely that would be, "Be Coooooool"  not be calm :)
[16:52] <Laney> you people are too old for me
[16:52] <davmor2> willcooke: Followed by Heeeeeeeeeeeyyyyyyyyyy
[16:52] <willcooke> \o/
[16:53] <davmor2> you Laney 's get off my lawn
[16:54]  * Laney tears it up with a mini moto
[17:06] <davmor2> Laney: hahaha mini moto, now I have an image of you something like this http://www.aboutfacesentertainers.com/images/clowns/mayhem/may_g_little_bike.jpg
[17:11] <ogra_> lol
[17:23] <willcooke> g'night all
[19:02] <mitya57> bregma, any update on https://code.launchpad.net/~mitya57/compiz/switcher-plugins-in-default/+merge/262518 review?
[21:22] <Noskcaj> robert_ancell, adding a libcanberra build-dep to gnome-clocks fixes the current ftbfs. should the dep be in gnome-clocks or gsound?
[21:23] <robert_ancell> Noskcaj, I'm looking at it right now and scratching my head because neither gnome-clocks or gsound appears to require a dep on it
[21:25] <robert_ancell> I'm wondering if another dependency requires it and is missing the dep
[21:27] <robert_ancell> aha, it is in /usr/share/vala/vapi/gsound.deps
[21:27] <robert_ancell> So it should be in libgsound-dev
[21:27] <robert_ancell> Though perhaps the .deps shouldn't include it
[21:35] <robert_ancell> Noskcaj, yeah, looks like a bug in libgsound - I'll patch it
[21:35] <Noskcaj> ok, thanks
[21:39] <Noskcaj> Do we want to do the gegl transition ahead of debian?
[21:45] <robert_ancell> Noskcaj, I wasn't sure. It didn't seem like too much work as long as Debian catches up and we can sync with them afterwards.
[21:45] <robert_ancell> I have no idea what timeframe Debian is following on it
[21:46] <robert_ancell> https://bugzilla.gnome.org/show_bug.cgi?id=752645
[21:46] <robert_ancell> Fixed in gsound 1.0.1-0ubuntu2
[21:49] <Noskcaj> robert_ancell, I assume it's just because the gimp maintainer hasn't replied. I'll see if i can find him
[22:06] <ochosi> Sweet5hark: hey! is there already some sort of ETA for LO 5.0 (and then in wily)?