mir needs to be "robustified" against the double on and double off
calls. Even when I account for this though, the system will still run
into problems.

I still have reason to suspect that when the dbus message to unity mir
to turn the display on is received, the system is still in the suspend
state. Still trying to verify that when the display on message is sent,
the system is guaranteed to be in the 'active' state before the message
is sent.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258655

Title:
  Abort when blanking/unblanking screen; exception thrown from
  mir::graphics::android::HWCCommonDevice::mode(MirPowerMode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1258655/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to