** Changed in: mir
Milestone: 0.25.0 => 0.26.0
--
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/1588237
Title:
Inconsistent behaviour of Num Lock
Status in Canonical System Image:
Confirmed
Status in Mir:
In Progress
Status in mir package in Ubuntu:
Triaged
Bug description:
How to reproduce:
M10 with external Keyboard and Screen, after restart on OTA11.
To use numbers in the unlock screen, the num key has to be active.
After unlocking, use a search field in the homescope or any other scope.
Expected behaviour:
The numblock should work, as the num key is still active.
Actual behaviour:
The numblock only works, when you deactivate the num key.
This is the same for the browserbar or the telegram chat.
After some time, the behaviour changes, so the numblock behaviour seems to be
inconsistent.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588237/+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
