isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-25 17:40:40 -05:00
Code Issues Packages Projects Releases Wiki Activity

backends/x11: Do not reload keymap on new keyboard notifications

Browse Source 
XkbNewKeyboardNotify informs the client that there is a new keyboard
driving the VCK. It is essentially meant to notify that the keyboard
possibly has a different range of HW keycodes and/or a different
geometry.

But the translation of those keycodes remain the same, and we don't
do range checks or geometry checks (beyond using KEY_GRAVE as "key
under Esc", but that is hardly one). It seems we can avoid the
busywork that is releasing all our passive grabs, reloading the keymap
and regenerating the keycombos and restoring the passive grabs.

Closes: https://gitlab.gnome.org/GNOME/mutter/issues/398
This commit is contained in:
Carlos Garnacho 2019-05-16 12:25:47 +02:00
parent e8bca5052a
commit b01edc22f3
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/backends/x11/meta-backend-x11.c
View File

@ -357,7 +357,6 @@ handle_host_xevent (MetaBackend *backend,
{ {
switch (xkb_ev->any.xkb_type) switch (xkb_ev->any.xkb_type)
{ {
case XkbNewKeyboardNotify:
case XkbMapNotify: case XkbMapNotify:
keymap_changed (backend); keymap_changed (backend);
break; break;