So my problem noted in #8 was just a mis-match of packages on my system. Cannot reproduce with xenial + silo 021, nor with on-system builds of lp:mir, lp:mir/0.18, or lp:mir/0.17.
After standup today, it seems like we weren't able to reproduce the problem, provided that we had updated systems, and were using the (unintuitive) --vt switch properly (which became a bit more unintuitive starting at 3098). Hopefully everyone else comments below with further details of their testing. The decision in the standup today was to proceed with release -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp