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
** 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
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;
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
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:
** 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
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
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
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
** 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:
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
11 matches
Mail list logo