Needs retesting. The symptoms might have changed: bug 1620934
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ...
nv50_flus
Done. There doesn't appear to be any way that Mir itself can screw up
that call.
It's possible qtmir might be messing up with an incorrect 'this' pointer
to the Mir DisplayBuffer. But I think much more likely that it's a
nouveau driver bug. If it wasn't then we'd be seeing similar crashes
with int
We should sanity-check the correctness of the eglMakeCurrent call in Mir
src/server/graphics/nested/display_buffer.cpp:62
But other than that, it seems to be purely a nouveau bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Tags added: unity8-desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ...
nv50_flush() ... pushbuf_kref()
To manag
** Summary changed:
- unity8 crashed with SIGSEGV
+ unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush()
... pushbuf_kref()
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553328
Title:
unity8 crashed with SIGSEGV
To manage notifications about this bug go to:
https://bug
