After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 602137 - Shortcuts are broken for configurations using 1st non-latin group
Shortcuts are broken for configurations using 1st non-latin group
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 599894 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-11-16 21:14 UTC by Sergey V. Udaltsov
Modified: 2018-04-15 00:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sergey V. Udaltsov 2009-11-16 21:14:44 UTC
The bug #162726 when fixed, created a serious issue for people having several layout, with the first layout non-latin. Now, when processing shortcuts, gtk only looks in the first XKB group.

For example, if you have xkb layouts us,ru - your shortcuts (Ctrl-A, Ctrl-C,
...) work fine.

If you have ru,us (swapped) - shortcuts do not work at all. Because the first
group contains cyrillic characters.

The patch that broke it (most impatient users can revert and rebuild gtk) is here: http://git.gnome.org/cgit/gtk+/commit/?id=17f8a2c23aba669cbcf7a5c9fc650d8dee78d7f6
Comment 1 Pozsár Balázs 2010-03-03 17:48:29 UTC
This is not only a problem with non-latin layouts. If your primary layout is Hungarian, your secondary is US english, you are using the US one, and press ^] (telnet commandline) in gnome-terminal, it will send the 'ú' character instead of ^]. The ']' is in the same place on the english keyboard as the 'ú' character on the hungarian keyboard.
This is a serious usuability problem, please fix it. Reverting http://git.gnome.org/cgit/gtk+/commit/?id=17f8a2c23aba669cbcf7a5c9fc650d8dee78d7f6 fixes it.
Comment 2 Christian Persch 2010-03-17 19:27:48 UTC
*** Bug 599894 has been marked as a duplicate of this bug. ***
Comment 3 Matthias Clasen 2018-02-10 05:26:43 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 4 Matthias Clasen 2018-04-15 00:37:55 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new