[09:55] <alan_g> greyback: congratulations! miral integration has passed QA
[09:55] <greyback> alan_g: hurray!
[10:11] <davmor2> alan_g, greyback: now don't make it sound like it is a fluke or we might go back and look at it again ;)
[10:11] <greyback> :D
[10:12] <alan_g> so true!
[10:18] <greyback> alan_g: fyi https://bugs.launchpad.net/ubuntu/+source/miral/+bug/1651384
[10:18] <ubot5`> Ubuntu bug 1651384 in miral (Ubuntu) "[MIR] miral" [Critical,New]
[10:18] <greyback> need miral to be in main before unity8 can use it
[10:18] <alan_g> Oh yeah, I'd forgotten we'd need that.
[10:20] <alan_g> greyback: can I help? Or is it just another wait for the wheels to turn?
[10:21] <greyback> alan_g: the later, I think that's all the paperwork needed
[11:57] <dandrader> alan_g, hi, did you read my mail about the double-lock issue?
[11:58] <alan_g> dandrader: sorry, I forgot about it
[12:02] <alan_g> dandrader: I see. Yes, force_close() shouldn't be calling a function from shell::WindowManager.
[12:03]  * alan_g wonders why he's not hit that
[12:07] <dandrader> alan_g, should I file a bug?
[12:08] <alan_g> please - I'll get to it real soon
[12:14] <dandrader> alan_g, https://bugs.launchpad.net/miral/+bug/1651422
[12:14] <ubot5`> Ubuntu bug 1651422 in MirAL "Double lock in force_close()" [Undecided,New]
[12:15] <alan_g> dandrader: thank you. Do you need the fix released? Or just committed for the time being?
[12:20] <dandrader> first option is best, of course. but it's not blocking me. worst case I add a work around in qtmir (ie, no lock that call)
[12:20] <dandrader> alan_g, ^
[12:24] <alan_g> dandrader: if you do a workaround I suggest using "#if MIRAL_VERSION <= MIR_VERSION_NUMBER(1, 0, 0)"
[12:24] <dandrader> alan_g, right, good point
[12:36] <dandrader> alan_g, so the next miral release is gonna be 1.0?
[12:36] <alan_g> dandrader: the last one was
[12:36] <dandrader> oh
[12:37] <dandrader> alan_g, is it in zesty?
[12:38] <alan_g> yes
[12:38] <alan_g> http://voices.canonical.com/alan.griffiths/2016/12/19/miral-1-0/
[12:38] <dandrader> landed today, right. because it wasn't there yesterday
[12:38]  * dandrader upgrades
[12:39] <alan_g> landed yesterday, my afternoon
[12:50] <alan_g> dandrader: https://code.launchpad.net/~alan-griffiths/miral/fix-1651422/+merge/313609
[17:33] <alan_g> camako: the discussion comment I promised you yesterday: https://code.launchpad.net/~cemil-azizoglu/mir/mirsurfacespec-deprecation-2/+merge/313451/comments/814567
[17:34] <camako> Thanks. I was just reading it.
[17:34] <alan_g> 8-)
[18:31] <_javier4_> Hi guys, I'm porting a device and now I'm stuck at the ubuntu animation boot logo (ubuntu text with dots moving). compositor log doesn't help, and now I'm seeing this messages in dmesg
[18:31] <_javier4_> (1)[2353:VSyncThread_0][DISP][mtk_disp_mgr_ioctl #1956]ERROR:[session]ioctl not supported, 0x40104fd5
[18:31] <_javier4_> (1)[2361:Mir/Comp][DISPCHECK]primary_display_switch_mode require sess_mode DIRECT_LINK
[18:33] <_javier4_> repeated many times. Are they meaningful for my problem?
[18:43] <greyback> _javier4_: sounds possible yes. Can you share the output of "/system/bin/logcat" and "$HOME/.cache/upstart/unity8.log" please
[18:44] <greyback> /var/log/lightdm/unity-system-compositor.log too
[18:50] <_javier4_> greyback, unfortunately logcat returns nothing, these are the logs you asked for
[18:50] <_javier4_> http://pastebin.com/50CmQMTz
[18:50] <_javier4_> http://pastebin.com/atis2u9q
[19:12] <greyback> _javier4_: hmm unity-system-compositor does bring up GL ok (lots of warnings, but it appears to work since you see the splash)
[19:12] <greyback> but something is wrong with unity8
[19:12] <greyback> it is a mir server, which connects to unity-system-compositor (as a nested mir server)
[19:12] <greyback> seems to fail to connect/start
[19:12] <greyback> am unsure why
[19:15] <_javier4_> is there something I can do to supply more debug messages?