desktop-packages team mailing list archive

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

Verified fixed on two i945 systems. Probably the Mesa 10.5 upgrade in
vivid fixed this.

Unity8 on these older systems is a bit slow and I can't get through the
welcome wizard fully. But it's not crashing any more so bug fixed!

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

** Changed in: mesa (Ubuntu)
       Status: New => Fix Released

** Changed in: mesa (Ubuntu)
   Importance: Undecided => High

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

** Changed in: qtmir
       Status: Confirmed => Invalid

** Changed in: mir (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: qtmir (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1408910

Title:
  (i945 only) 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:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid

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