Unity8 on Vivid doesn't boot, due to mesa2 and mesa3 client platforms being installed at the same time

[Andrea Bernabei]

After setting up a laptop from scratch with
Vivid 15.04 + Overlay PPA + unity8-desktop-session-mir package
I could not get Unity8 to boot

turns out it is because I had both mesa2 and mesa3 client platforms installed.

I did not install them, so they have been either pulled in by desktop-session-mir, or seeded in Vivid, or something along those lines.

alan_g could also reproduce the same bug on his machine.

[Alan Griffiths (alan-griffiths)]

I'm not sure of the exact sequence of events but there's a crash in GetXcbConnection() that gets fixed by "apt-get remove mir-client-platform-mesa2".

I know this mesa.so.2 leaks a dl handle and symbols in ways that are problematic. So we probably ought to find some way to uninstall it with more recent installs. I'm not sure what debian incantation is needed (or where to put it).

[Andrea Bernabei (faenil)]

I'm not even sure it's a Vivid specific bug...

[Alan Griffiths (alan-griffiths)]

...only vivid has mir-client-platform-mesa2

[Andrea Bernabei (faenil)]

alright, then it must be vivid-only. I think when I had this issue for the first time I was installing unity8 on Wily (or xenial), but I might be misremembering ;)

[Daniel van Vugt (vanvugt)]

Sounds like bug 1526658. And the description suggests Andrea has already stumbled on the workaround/fix.