Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1549701
Title:
Sometimes devices don't suspend - display turns back on immediately
Status in Canonical System Image:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in unity-system-compositor package in Ubuntu:
Confirmed
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
current build number: 267
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
it happens also on arale.
sometimes the screen lock timeout is not honoured and the devices
don't suspend when the lock timeout expires (display doesn' t turn
off)
$ sudo powerd-cli list
[sudo] password for phablet:
System State Requests:
Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1
Steps to reproduce on arale:
1. Turn on the screen
2. Touch the circular touch button at the lower part of the device
3. Press/release the power button to turn off screen
4. Release the circular touch button
Expected results: The screen turns off and further on/off cycles work properly
Actual results: The screen stays on and attempts to turn it off fail
The touchscreen is handling the circular button and emits a key down event.
When turning the screen of the touch screen device is turned off too. Mir is
not aware of the touchscreen being off. So meanwhile the repeat handling kicks
in and emits key events. This makes USC turn the screen back on again.
The touchscreen driver does not notice that the circular button is still
held. So still no release event is sent.
We could fix this by:
- fixing the touchscreen driver to release any touch contacts or buttons
pressed, when the device is turned off (something the bluetooth stack seems to
do on some devices)
- sidestep the problem by making usc only react to press events as a wake
trigger and make repeat and release events only reset the inactivity timer
- give mir the knowledge that the disabled output also disables the
touchscreen (a connection we need to be aware of to get the mapping of touch
screen coordinates onto scene coordinates right), hence remove the device and
thus turn of any repeat key handling attached to that device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+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
