[08:25] <alan_g> alf_: Happy? https://code.launchpad.net/~alan-griffiths/mir/introducing-mir_test_framework-main/+merge/262998
[08:26] <alf_> alan_g: +1
[08:30]  * alan_g wonders if he can "fix" test_client_cursor_api.cpp before vacation
[12:55] <alf_> anpok: Anything more for nested-client-to-display-buffer-latency-benchmark?
[12:58] <anpok> alf_: ok
[12:58] <alf_> anpok: thanks
[14:06] <seb128> AlbertA, hey, thanks for the help yesterday, I'm still looking at the issue ... do you know why the vt change ioctl wouldn't work
[14:33] <AlbertA> seb128: no prob
[14:33] <AlbertA> seb128: I thought it was the race where agettty got the VT before mir
[14:44] <seb128_> re
[14:44] <seb128_> AlbertA, sorry, I disconnect
[14:45] <seb128_> so making progress
[14:45] <seb128_> in fact unity8 does start on the usc instance on vt8
[14:45] <seb128_> it's only that vt switch fails
[14:45] <seb128_> so vt7 goes back to lightdm making it look like the session failed
[14:45] <seb128_> also the usc.log is on "pause"
[14:48] <seb128_> but going to vt8 make unity8 load and usc
[14:48] <AlbertA> seb128_: is it possible to change the VT agetty  uses?
[14:53] <seb128_> AlbertA, do you think it's also a case of agetty conflict?
[14:53] <seb128_> lightdm log has warnings about the vt console switch ioctl not handled
[14:54] <AlbertA> seb128_: yeah I'm wondering if that's because agetty got the VT first
[14:54] <seb128_> is there any way to change agetty?
[14:54] <seb128_> need to go for half an hour, going to read backlog and look a bit more then
[14:54] <seb128_> thanks!
[15:56] <racarr> GOod morning!
[21:07] <SturmFlut> Is Mir-on-X what I think it is?
[21:17] <anpok> let me read your mind..
[21:17] <anpok> ... yes
[21:19] <conyoo> hmm... let's try Mir on X on XMir
[21:23] <anpok> if you are on intel you might need a new mesa