Yeah I figured it out. Non rootless (rooted!) XMir wants to decide the
display power state (DPMS). Unity8/QtMir never had to deal with clients
doing that before.
Longer term Unity8 should filter such requests as it's quite rude for an
app to be able to turn off your display on you, but I've a branch up to
at least not crash.
I've more work to do on this though, as waking up the display isn't
working with that branch. To be continued
** Branch linked: lp:~gerboland/qtmir/fix-glcontext-loss-on-reconfigure
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521403
Title:
Unity8 crashes with SIGSEGV in Screen::makeCurrent
(./src/platforms/mirserver/screen.cpp:406)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1521403/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
