touch-packages team mailing list archive

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

Tested with mir-demos on the affected machine. Nesting works just fine
with the mir-demos.

This bug then is just Unity8/QtMir choosing EGL config modifications
that i945 systems can't support. Looking at the QtMir code, I would
hazard a guess that the request for 8 bit stencilling is unreasonable:

class MirGLConfig : public mir::graphics::GLConfig
{
public:
    int depth_buffer_bits() const override { return 24; }
    int stencil_buffer_bits() const override { return 8; }
};


** Changed in: mir
       Status: Triaged => Invalid

** Changed in: mir
    Milestone: 0.11.0 => None

** Also affects: qtmir
   Importance: Undecided
       Status: New

** Changed in: qtmir
       Status: New => Triaged

** Changed in: qtmir
   Importance: Undecided => Critical

-- 
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