Mir either has to expose the xkb_state (which we currently do not - and
might be only on the server) or provide the keysym text directly with
the event.
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Status: New => Confirmed
** Tags added: input
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1664610
Title:
qtubuntu sends wrong text as part of QKeyEvent
Status in mir package in Ubuntu:
Confirmed
Status in qtubuntu package in Ubuntu:
New
Bug description:
When using Unity7 or Plasma a key event created by Ctrl+C is
QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003")
But Unity8+ qtubuntu send to the application
QKeyEvent(KeyPress, Key_C, ControlModifier, text="c")
This is most likely because QMirClientInput::dispatchKeyEvent is using
xkb_keysym_to_utf8 to get the text of the event instead of using
xkb_state_key_get_utf8
This breaks for example Konsole that expects the correct text to be
sent.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1664610/+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
