Alan's enhanced fixed has now landed for Mir 0.20.0, which should
eliminate the need for the above workaround. Also backported in
preparation for Mir 0.19.1
** Also affects: mir/0.19
Importance: Undecided
Status: New
** Changed in: mir/0.19
Status: New => Fix Committed
** Change
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526658
Title:
Mir clients (including Unity8 itself) crash in XGetXCBConnection() if
m
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.20.0
** Changed in: mir
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Updated workaround for xenial users who now have Mir 0.19.0:
$ sudo apt-get remove mir-client-platform-mesa3 mir-client-platform-
mesa2 mir-client-platform-mesa1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
mir (0.19.0+16.04.20160128-0ubuntu1) xenial; urgency=medium
** Changed in: mir
Status: Fix Committed => Fix Released
** Changed in: mir (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Branch linked: lp:~alan-griffiths/mir/fix-1526658
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526658
Title:
Mir clients (including Unity8 itself) crash in XGetXCBConnection() if
multiple ver
We now have a /future/ fix landed. But that only works for the cases
where the older Mir version is 0.19 and you have something newer than
that installed on top of it. Still lacking a retrospective fix, which
may just need to be a script or deb rules to force out the old broken
packages like: sudo
