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 129918 - Doesn't obey remapped keyboard from GNOME
Doesn't obey remapped keyboard from GNOME
Status: RESOLVED DUPLICATE of bug 103331
Product: metacity
Classification: Other
Component: general
2.6.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2003-12-23 20:59 UTC by Sebastien Bacher
Modified: 2005-08-15 01:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2003-12-23 20:59:05 UTC 
This bug was originally reported in the Debian BTS:
http://bugs.debian.org/223722

"I switched to the DVORAK layout in GNOME, but metacity's keyboard
shortcuts still respond to the old (qwerty) layout."
Comment 1 Rob Adams 2003-12-23 21:40:17 UTC 
funky.  Metacity stores integer keysyms internally to maintain its
keyboard shortcut map.  I was under the impression that, for example,
a "a" was always the same keysym no matter what the keyboard layout
was.  Is this not the case?
Comment 2 Havoc Pennington 2003-12-24 04:34:01 UTC 
Metacity relies on the keysym <-> keycode map though, in order to call
XGrabKey(). There's another open bug already I think that it doesn't
properly react to keyboard mapping change events (MappingNotify IIRC).
There's code that's supposed to react to these events, but it must not
work.
Comment 3 Rob Adams 2004-01-04 04:00:44 UTC 
probably not the problem but in keybindings.c (reload_keymap)
(display->max_keycode - display->min_keycode) in the call to
XGetKeyboardMapping should be (display->max_keycode -
display->min_keycode + 1)
Comment 4 Elijah Newren 2004-10-14 21:13:06 UTC 
See also bug 103331.
Comment 5 Elijah Newren 2004-10-14 21:19:02 UTC 
For the problem pointed out by Rob in comment 3, I filed bug 155427.
Comment 6 Elijah Newren 2005-01-26 19:17:56 UTC 
Since Rob's fix has been applied, I believe the rest of this bug is just a
duplicate of 103331, so I'm going to mark it as such.

*** This bug has been marked as a duplicate of 103331 ***