[07:16] <alf_> duflu: When you get some time can you please check if https://bugs.launchpad.net/mir/+bug/1352772 is fixed for you too?
[07:16] <ubot5`> Ubuntu bug 1352772 in Mir "gdb mir_demo_server_shell takes a very long time to start (over a minute)" [Medium,New]
[07:17] <duflu> alf_: It was still very slow a few days back. Will retest
[07:20] <duflu> RAOF: What happened to your "link to libmirplatform properly" branch?
[07:20] <duflu> Can't see it having landed
[07:24] <duflu> alf_: Umm, maybe. I seem to have overcommitted to too many activities again
[07:27] <RAOF> duflu: It ran into awkwardness - specifically, the wonders of the protobuf singleton (can we remove that?)
[07:28]  * duflu shrugs. Not wanting to commit to more threads of discussion
[22:47] <bregma> anyone know why unity-system-compositor would fail opening the DRM device http://paste.ubuntu.com/8322285/ ?
[22:50] <RAOF> bregma: Because Mir hasn't managed to find a DRM device that has any outputs available.
[22:50]  * bregma thinks that doesn't really help much
[22:51] <bregma> would that be because the guy is trying to run in a VM?
[22:51] <RAOF> That's entirely possible.
[22:52] <RAOF> I think the vmware drm module doesn't expose any connectors, tripping that check.
[22:52] <RAOF> I *also* thought we had removed that check because the vmware drm module doesn't expose any connectors.