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 intel and radeon, but we don't. ** Changed in: libdrm (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1553328/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
