touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #62140
[Bug 1408910] Re: (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)
The last time I tested those systems the main blocker I saw was our mesa
package reporting a too low OpenGL version (the ES support would be fine
enough for QtQuick btw). After some digging it seemed that the GL
version is limited to 1.X, to avoid usage of certain full screen effects
in unity7.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir 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:
Confirmed
Status in Qt integration with the Mir display server:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in qtmir 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
References