Comment 21 for bug 23244

I've just upgraded from Dapper to Hardy and I'm also hit by this bug. Currently I'm experimenting with the Colemak layout and changing back-n-forth from Qwerty. Dapper had no problem with this. In Hardy I can't do this because the Ctrl'ed keys don't change in GTK apps, they always stay Qwerty (or always stay Colemak, whichever is the first one loaded). However, these keys do work correctly in other apps (e.g. plain old xterm).

It was hardly a few years ago that X developers finally made it possible to load multiple layouts and switch with a shortcut key that works always and immetiately. Now we're back to the old ages where the only way to change the layout is to execute a setxkbmap or xmodmap command each time, which might take some time depending on the system load, connecting to a shortcut key is tricky and does not always work (e.g. shortcut keys are usually not working if an app has its menu open), and is not compatible with the Gnome keyboard applet.

I'm pretty much shocked to see that this bug has "importance: low". Do you really mean it?
- Keyboard is the device I'm using 8 hours a day, and I'm sure I'm not the only guy with this strange habit.
- It's clearly a regression from old Ubuntu versions.
- GTK apps interpret keypresses differently than other apps, which is a blocker on its own in my opinion. (The same physical keypress should send the same logical keystroke to all apps.)
- A cool feature of X is unusable due to this bug and switching layouts becomes painful as it was in the old ages.
- Gnome keyboard switcher app is unusable due to this bug.
- 23 duplicates were reported so far. This makes me feel that fixing this bug is important for a lot of people.