touch-packages team mailing list archive

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

I'm not quite sure what QtMir is doing to trigger this. I've tried hacks
to Mir directly to try and emulate what it might be doing, but my hacks
result in nested servers starting and running perfectly still.

Something about QtMir I'm failing to emulate...

** Tags added: nested

-- 
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:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

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:
  ~~~
  ()
  [1420794321.348507] (II) SharedLibrary: Loading libmirplatform5driver.so
  qtmir.mir: MirServer created
  [1420794321.423199] (II) Server: Starting
  libEGL warning: unsupported platform (null)
  ERROR: /build/buildd/mir-0.10.0+15.04.20150107.2/src/server/graphics/nested/nested_display.cpp(85): Throw in function void mir::graphics::nested::detail::EGLDisplayHandle::initialize(MirPixelFormat)
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
  std::exception::what: Failed to create shared EGL context

  ERROR: QMirServer - Mir failed to start
  terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >'
    what():  Cannot use configuration before apply_settings() call
  ~~~

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

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