This means that while the device was unresponsive neither unity-system- compostior nor qtmir ( in unity8 process) got any input events at all.
So this rules out at least qtmir and unity8. I think the next step is to directly monitor the evdev files to see if anything at all comes out of them while the device is in this unresponsive state. -- 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
