[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
** Changed in: mir Milestone: 0.12.0 => 0.13.0 -- 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_error 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 >' 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
Possible duplicate: bug 1418456 . It has some interesting backtraces and valgrind logs. -- 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_error 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 >' 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
** Changed in: mir Milestone: 0.11.0 => 0.12.0 -- 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_error 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 >' 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
i can also reproduce this issue with the daily images on my eeepc (with i945 graphics) -- 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_error 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 >' 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
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_error 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 >' 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
Reproduced on a third machine, where I could get a copy of the log file off. ** Description changed: - 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 + 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_error + 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 >' + what(): Cannot use configuration before apply_settings() call + ~~~ I've also verified mir_proving_server with mir_demo_client_* runs fine in another VT. ** Attachment added: "unity8.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408910/+attachment/4294511/+files/unity8.log ** Changed in: mir Status: Invalid => Incomplete ** Changed in: mir Status: Incomplete => Confirmed ** Changed in: qtmir Status: Triaged => Confirmed ** Changed in: qtmir (Ubuntu) Status: Triaged => Confirmed ** Changed in: unity8 (Ubuntu) Status: Triaged => Confirmed ** Changed in: mir Milestone: None => 0.11.0 ** Changed in: mir Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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_error 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 >' 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
The problem could also be the incorrect selection of a MirPixelFormat. -- 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. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1408910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
** Description changed: 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? -- 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. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1408910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
Hmm, actually this has only been reported on i945 systems so far (me and another person in: https://bugs.launchpad.net/mir/+bug/1275398/comments/20 My Haswell desktop works fine with the same image. Maybe we're missing something in our relatively recent mesa patches to support i945?... -- 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: 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
** Description changed: - Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. + 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? -- 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: 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
