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 103331 - switching keyboard layouts with gkb kills GUI keyboard shortcuts
switching keyboard layouts with gkb kills GUI keyboard shortcuts
Product: metacity
Classification: Other
Component: general
Other other
: Normal major
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
: 129918 356146 (view as bug list)
Depends on:
Reported: 2003-01-13 03:49 UTC by Havoc Pennington
Modified: 2020-11-06 20:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Havoc Pennington 2003-01-13 03:48:26 UTC
Bugzilla-Product: metacity

  Please see
  for the original bug report.
   (This is a batch-forwarded bug, if it doesn't make sense let me know.
   The bug was forwarded because it's a feature request and we don't
   want to maintain the custom feature or UI change in Red Hat patches,
   or because we don't expect to fix it ourselves but thought it might be
   a legitimate issue. It was not obviously a packaging or Red Hat specific bug.
   If you would rather not be forwarded such bugs, please advise. Thanks)

------- Bug moved to this database by 2003-01-12 22:48 -------

Reassigning to the default owner of the component,

Comment 1 Havoc Pennington 2003-09-25 02:18:18 UTC
This is presumably a bug in keymap change notification handling in
keybindings.c, it should be easy to figure out with some verbose debug

I guess it could also just be a problem with the exact keymap that
gets switched to.
Comment 2 Fernando Herrera 2004-02-12 08:36:19 UTC
Confirmed on GNOME 2.5:
Steps to Reproduce:
1. make a GUI key shortcut with Preferences->Keyboard shortcuts
2. install the gkb applet with two keyboard layouts
3. switch from one layout to another using the gkb applet

Actual Results:  the specified GUI keyboard shortcuts are lost (they
don't work
Comment 3 Tessa Lau 2004-06-16 21:46:16 UTC
This isn't a metacity bug.  I can repro in GNOME 2.6 (Debian unstable) using the
FVWM window manager and the "ida" application.

I use gnome-keyboard-applet to switch between "us" and "dvorak" keymappings.   
I have it set to use the same mapping for all windows, not a different mapping
per window.  "us" is the default.  The bug is that Ida always uses "us"
keymappings, even after I've switched to "dvorak" and the gnome-keyboard-applet
is showing "dvorak".

I see similar behavior for only the control-key combinations in any Wine or
Crossover Office applications (e.g., PowerPoint).  The non-modified keys obey
the selected layout, but control-modified keys always use the default layout.
Comment 4 Elijah Newren 2004-10-14 21:13:02 UTC
See also bug 129918.
Comment 5 Elijah Newren 2005-01-26 19:17:58 UTC
*** Bug 129918 has been marked as a duplicate of this bug. ***
Comment 6 Elijah Newren 2005-10-07 16:08:25 UTC
Remove old target milestones on old bugs; sorry for the spam.
Comment 7 Owen Taylor 2009-11-20 21:30:22 UTC
*** Bug 356146 has been marked as a duplicate of this bug. ***
Comment 8 Owen Taylor 2009-11-20 21:53:42 UTC
I haven't investigated this in detail, but I don't think this (or at least the behavior described in comment 3 and bug 129918) has anything to do with reloading keymaps. When you switch between Xkb layouts, that isn't a change in keymap; instead different parts of the same keymap are used.

But the keyboard handling in Metacity is very simple and doesn't handle things like multiple different layouts.

There is also the issue that for two completely different keymaps like a 'us' keymap and a 'ru' keymap, you actually want the behavior where the key shortcut works across the two groups. See massive discussion in bug 162726.
Comment 9 André Klapper 2020-11-06 20:05:19 UTC is being replaced by We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at

Thank you for reporting this issue and we are sorry it could not be fixed.