[01:57] <RAOF> Grr.
[01:58] <RAOF> Why does this test sometimes fail when you send and event on surface creation? Oh, because there's an entirely unnecessary EXPECT_CALL() in there which doesn't match and so is an error.
[02:00] <RAOF> This is one of the things I don't like about our testing; we routinely overspecify behaivour, so entirely benign changes become testsuite failures.
[02:06] <duflu> Cosmic rays
[02:07] <duflu> Quantum fluctuations
[02:07] <duflu> Or programmer error
[02:07] <duflu> (not necessarily the present programmer)
[02:24] <duflu> New wily wallpaper!
[02:32] <duflu> I just wish we had slightly higher quality jpgs. Like gnome-wallpapers usually does
[02:56] <duflu> robert_ancell: Cursor fix landed for Mir 0.17. It seems to work even better than the workaround (which still has moments of invisibility)
[02:57] <robert_ancell> duflu, \o/ awesome
[02:58] <robert_ancell> duflu, Mir 0.17 will be for x-series?
[03:02] <duflu> robert_ancell: Ask camako I guess
[03:03] <duflu> Although he's started the release process for 0.16.1. If it was important then it could go in there
[03:03] <duflu> We have a bunch of important fixes not released yet actually: https://launchpad.net/mir/+milestone/0.17.0
=== chihchun_afk is now known as chihchun
[06:57] <RAOF> LOOK ON MY AWK, YE MIGHTY, AND DESPAIR!
[07:32] <anpok_> RAOF: yeah we should know better..
[07:32] <duflu>   /awk/ { FTW }
[08:08] <RAOF> Alright.
[08:09] <RAOF> While I was waiting for CI, we have, as promised, a new DSO versioning guide proposal: https://code.launchpad.net/~raof/mir/new-dso-versioning-policy/+merge/273186
[08:09] <anpok_> uh
=== DalekSec_ is now known as DalekSec
=== Mirv_ is now known as Mirv
=== tjaalton_ is now known as tjaalton
=== chihchun is now known as chihchun_afk
[11:00] <sil2100> alf_: ping
[11:00] <sil2100> alf_: hey! It seems that your recent unity8+u-s-c+powerd landing caused issues on mako
[11:01] <sil2100> alf_: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1502093
[11:01] <ubot5`> Ubuntu bug 1502093 in Canonical System Image "unity8 crash on mako rc-proposed/ubuntu with latest unity8/mir/powerd" [Critical,New]
[11:41] <Saviq> mzanetti, ↑
[11:44] <Saviq> sil2100, I think it might be mir landing, too
[11:44] <Saviq> just checking which package actually breaks it
[11:46] <sil2100> Yeah...
[11:47] <Saviq> u-s-c fine
[11:47] <Saviq> unity8 fine
[11:49] <Saviq> did mir 0.16.1 not go through citrain?
[11:50] <Saviq> ah d'oh
[11:50] <Saviq> same silo
[11:56] <Saviq> hum hum
[11:57] <Saviq> upgraded all mir pkgs, working...
[11:58] <Saviq> UITK could be the actual problem after all
[11:58] <Saviq> or restart lightdm not enough to trigger bug
[11:59] <Saviq> yup
[11:59] <Saviq> sil2100, UITK culprit
[11:59] <Saviq> not mir
[12:02] <Saviq> greyback_, uitk culprit, not mir ↑ https://requests.ci-train.ubuntu.com/#/ticket/433
[12:02] <kgunn> Saviq: huh
[12:02] <kgunn> jibel: ^
[12:02] <Saviq> confirming in a mo
[12:02] <greyback_> Saviq: +1 that the mir updates had no impact
[12:02] <greyback_> yeah, just installed UITK, now crashy
[12:03] <Saviq> wonder if both needed to show problem
[12:03] <Saviq> reflashing again
[12:03] <Saviq> actually I got flo clean still
[12:03] <kgunn> oh and alf_ ^
[12:04] <Saviq> trying there
=== alan_g is now known as alan_g|lunch
[12:06] <Saviq> yup, uitk enough to make it die
[12:06] <greyback_> it's crashing in a render thread, which would suggest to me it's a gl error
[12:06] <sil2100> Saviq: oh my
[12:07] <greyback_> "[UbuntuShape] Added mipmap based anti-aliasing fallback" would be my first suspicion
=== alan_g|lunch is now known as alan_g
=== marcusto_ is now known as marcustomlinson
[13:12] <jibel> kgunn, great :/
[13:13] <kgunn> jibel: lol...yeah
[13:13] <kgunn> at least we got it surrounded quickly
[13:54] <alan_g> greyback_: I just noticed that Mir doesn't have the X cursors available on phone and falls back to the famous arrow. I assume that the plan is for pocket desktop is supply its own images?
[13:55] <greyback_> alan_g: unity8 is using cursors from the old xcursors theme unity7 uses
[13:56] <greyback_> it's working in our mousePointer stuff
[13:59] <alan_g> OK. I hope
[14:43] <dandrader> alan_g, so qtmir calls mir::Server::the_cursor()->hide(). and it works. but once I connect an external monitor to my laptop the mir cursor becomes visible again
[14:43] <dandrader> alan_g, is that a bug?
[14:44] <alan_g> dandrader: brb
=== chihchun_afk is now known as chihchun
[14:55] <alan_g> dandrader: it is hard to say. There very few tests to define the correct behaviour of cursors. And I'm wading through a lot of "obviously wrong" behaviour and adding tests. I deduce that something is calling cursor->show(), but whether it should...
[14:57] <dandrader> alan_g, my point is: should qtmir call cursor->hide() whenever a new display is connected or should I report a bug?
[14:57] <dandrader> alan_g, the first option looks like a work around in my opinion....
[14:58] <alan_g> dandrader: I suspect there's a mechanism missing to tell the cursor controller that the cursor should be off. So file a bug.
[14:59] <dandrader> alan_g, ok
=== dandrader is now known as dandrader|afk
=== chihchun is now known as chihchun_afk
=== dandrader|afk is now known as dandrader
=== alan_g is now known as alan_g|EOW
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader