Gerry collected this helpful dbus log http://pastebin.ubuntu.com/6567567/ (also attached) that shows we get an on, on message from dbus.
the error shown: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >' what(): could not activate surface with eglMakeCurrent will happen if mc::Compositor::start() is called twice in succession. Still trying to figure out if the on, on message from dbus is something we should handle, or if something is getting confused somehow. ** Attachment added: "dbus-log.txt" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1258655/+attachment/3928868/+files/dbus-log.txt -- 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
