We're needing more data on this bug, and we're going to eventually land the MP's to improve some reporting.
But this bug is critical, and we'd like to get information as soon as possible. _Only_ if you are willing to risk not getting autoupdates (and have to flash your phone in future) - you can try the improved reporting for mir & unity-system-compositor by installing https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-014 you'd need to be on OTA9.5 or latest rc-proposed image. If you install this ci-train silo and experience this bug, we are highly interested in the /var/log/lightdm/unity-system-compositor.log I'll follow up once we land these reporting improvements in the image and the silo is no longer needed. ** Changed in: mir Importance: High => Critical ** Changed in: unity-system-compositor Importance: High => Critical ** Changed in: mir (Ubuntu) Importance: High => Critical ** Changed in: unity-system-compositor (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528384 Title: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_power_mode_on) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
