The described behavior matches the way keyboard mapping is handled
within mir right now. Unity8 configures keymaps for each client surface.
Each client surface then has its own independent key state. Key state
here means the set of active modifier keys, including toggles like Caps
Lock, Num Lock. So it depends on which client sees
Mir 0.24 will change this behavior. It will default to have a per
keyboard device key state tracked and updated inside a mir server like
Unity8. Thus Num Lock will stay active after you switch between
surfaces. BUT: For that to work Unity8 need to configure its own server
side per device keymaps (they only default to us). Additionally we still
allow client side per surface keymaps. As of now the solution inside of
lp:mir and the presumptive 0.24 would not be capable of transfering the
current toggle state of Caps Lock or Num Lock when switching to an
application with a client side keymap. We already identified that
problem, and I plan to address that soon. But it might not make it into
0.24
As a short term fix I suggest to switch unity8 to only use server side
keymaps with 0.24, until this last problem is also addressed.
** Changed in: mir (Ubuntu)
Status: New => Confirmed
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)
--
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 the numblock
Status in Canonical System Image:
Confirmed
Status in mir package in Ubuntu:
Confirmed
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
