This seems to be another instance of bug 1550050, which involves the Mir
input subsystem sending key repeat events event after an input device
disappears. In this case the repeated key is the circular touch key at
the bottom of the MX4 (which is sent as left-meta). A fix for this is
included in the upcoming Mir 0.20.2 release.
I have added steps to reproduce this on MX4 in the description.
** Description changed:
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:
+ [sudo] password for phablet:
System State Requests:
- Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1
+ 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
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)
** Changed in: mir (Ubuntu)
Importance: Undecided => High
** Changed in: mir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549701
Title:
Sometimes devices don't suspend - display turns back on immediately
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
