In the spirit of wag in the stack I see the following in threads:
usc::MirScreen::set_screen_power_mode(MirPowerMode, PowerStateChangeReason) () usc::MirScreen::keep_display_on_temporarily() usc::MirScreen::dimmer_alarm_notification() is it possible a couple of these threads deadlock due to an unlucky timing of events, like the screen dimming as an sms comes in -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Shell not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Incomplete Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
