touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Also, you shouldn't need a depth buffer for a desktop either. Throwing
away that whole MirGLConfig, or at least loosening the restrictions
should solve the problem.

** Also affects: qtmir (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => Critical

** Changed in: qtmir (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1408910

Title:
  Ubuntu Desktop Next fails to start; just black screen and mouse
  pointer (unity8.log: std::exception::what: Failed to create shared EGL
  context)

Status in Mir:
  Invalid
Status in Qt integration with the Mir display server:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. So unity-system-compositor is working fine. Only the nested unity8 can't run:
  unity8.log: std::exception::what: Failed to create shared EGL context

  I've also verified mir_proving_server with mir_demo_client_* runs fine
  in another VT.

  I think this might be a new issue introduced by the upgrade to Mir
  0.10 last night?

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1408910/+subscriptions