https://bugzilla.redhat.com/show_bug.cgi?id=1974983
Peter Hutterer peter.hutterer@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|xkeyboard-config |gnome-shell Assignee|peter.hutterer@redhat.com |fmuellner@redhat.com CC| |adscvr@gmail.com, | |fmuellner@redhat.com, | |gnome-sig@lists.fedoraproje | |ct.org, jadahl@redhat.com, | |otaylor@redhat.com, | |philip.wyett@kathenas.org
--- Comment #7 from Peter Hutterer peter.hutterer@redhat.com --- Punting to GNOME Shell, at least initially because this seems to be a bug with the keyboard indicator.
Copy/paste from my upstream comment in https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/28...
Looks like the culprit is this line:
key <I592> { [ ISO_Next_Group ] }; // KEY_KBD_LAYOUT_NEXT
Having said that, the actual layout switching still works correctly, so this seems to be a bug with the layout indicator rather than the actual layout. I've played around a bit and it seems to only affect layout switches that require modifier state, so anything that is shift+something, alt+something or ctrl+something.
My guess would be that we have two keys both using ISO_Next_Group and the layout indicator doesn't handle this correctly in regards to modifier state. Either way, please file a bug against GNOME Shell, at least initially until it's further narrowed down.
Reproducing in Wayland is easy enough, edit /usr/share/X11/xkb/symbols/inet, comment that line out, then remove+add a layout in the GNOME control panel to force a keymap regeneration (or change some XKB option). This reliably reproduces the issue, depending on whether that line is commented out or not.
Bug cannot be reproduced in X because the keycode is out of range for X, so that's expected.