touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #134611
[Bug 1528384] Re: 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)
OK, we've made a point release of mir 0.19.1 and unity-system-compositor 0.4.1 which are now in the stable overlay.
Which means will be built into the next image and available on the rc-proposed channel.
Also, this should make it into the OTA9.5 release.
If you update and know you are on these point releases and are someone who is seeing this bug occur, please attach your /var/log/lightdm/unity-system-compositor.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in 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)
Status in Canonical System Image:
Confirmed
Status in Mir:
In Progress
Status in Unity System Compositor:
In Progress
Status in mir package in Ubuntu:
Confirmed
Status in unity-system-compositor package in Ubuntu:
Confirmed
Bug description:
Top crash over past week (ww02) on errors.u.c for rc-proposed
channels.
Started with u-s-c 0.2.0+15.04.20151216.1-0ubuntu1
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity-system-compositor. This problem was most recently
seen with version 0.2.0+15.04.20151216.1-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/7bcfcf599b35b264c0be45d5290ad9ae3c50adcf
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528384/+subscriptions
References