Thanks for all that info. With that I was able to get to the bottom of it pretty quickly:
Native Mir servers start fine (see unity-system-compositor.log in comment #4) but clients including the nested Untiy8 server fail to start: std::exception::what: Nested Mir Display Error: Failed to initialize EGL.: EGL_NOT_INITIALIZED (0x3001) If you look at the EGL docs, this error means eglInitialize was given an invalid display parameter. And that will happen if the version of Mesa you're using lacks the egl-platform-mir.patch (lacks Mir support). Turns out you're using a custom version of Mesa: 11.3~git160422173900.e85bef8~w~padoka0 which lacks Mir support. So of course Mir clients like the nested Unity8 server will fail to start. Please remove your custom Mesa version 11.3~git160422173900.e85bef8~w~padoka0, and replace it with the Ubuntu-provided Mesa: https://launchpad.net/ubuntu/+source/mesa And then you'll have no such problem. ** Changed in: mir Status: New => Invalid ** Changed in: mir (Ubuntu) Status: New => Invalid ** Changed in: unity8 (Ubuntu) Status: New => Invalid ** Changed in: unity8-desktop-session (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584635 Title: Black screen after logging in to Unity 8 [std::exception::what: Nested Mir Display Error: Failed to initialize EGL.: EGL_NOT_INITIALIZED (0x3001)] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
