With the way things are now, I'm pretty sure if we simply retried in mir after experiencing an error, we would hang the driver. Once we get these throws, the driver has essentially been put into an unrecoverable state. It seems Seth's investigation aligned with my intuition about the driver.
-- 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
