[19:28] <mterry> greyback: as a Mir knowledgeable guy...  is bug 1671214 surprising to you?  A known issue?
[19:29] <mterry> oh it is known -- bug 1670710
[19:33] <ltinkl> mterry, fix in the current silo
[19:38] <mterry> tedg: my look-at-mir UAL branch really helps snaps look nice in deb-unity8 -- they all launch in xmir now because nothing can plug unity8 interface
[19:38] <mterry> pretty please review and land
[19:42] <tedg> ltinkl: Oh, sweet!
[19:42] <tedg> mterry: K, cool. Did all the core apps pick up the "mir" interface?
[19:42] <mterry> tedg: Not sure, but does it matter?  None of the core apps plug unity8 right now because snapd doesn't let them
[19:42] <tedg> I hadn't looked to check recently, but last time I checked they hadn't.
[19:43] <mterry> Strict improvement
[19:43] <mterry> tedg: I mean they try to plug unity8, but snapd rejects it
[19:44] <mterry> so ual never sees that
[19:44] <tedg> mterry: Ah, well they do it here on my machine ;-)
[19:44] <mterry> tedg: do you have custom snapd?
[19:44] <tedg> Yeah
[19:44] <mterry> tedg: and custom unity8-session that exposes unity8 slot?
[19:44] <tedg> mterry: No, we're not using the connection yet. Just if they export it we pick it up.
[19:45] <mterry> tedg: ah didn't think snapd exported unconnected plugs
[19:47] <mterry> tedg: I didn't realize you were blocking on that.  I think that's wrong to do, but will try to do a survey of the core apps for ya