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 547451 - USA Dvorak keyboard layout does not remap control keys
USA Dvorak keyboard layout does not remap control keys
Status: RESOLVED DUPLICATE of bug 162726
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.22.x
Other All
: Normal minor
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-12 16:04 UTC by Tommy McGuire
Modified: 2008-08-12 21:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Tommy McGuire 2008-08-12 16:04:27 UTC
Please describe the problem:
From Ubuntu bug https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/255378

Binary package hint: gnome-control-center

Ubuntu 8.04.1 (currently up to date)

System > Preferences > Keyboard > Layouts > USA Dvorak

The control key mapping does not appear to be updated; i.e. after selecting USA Dvorak, the "i" key types "c" correctly, but with the Control key it inserts a tab (Ctrl-I) instead of a Ctrl-c.

Using "setxkbmap dvorak" from a terminal command line maps the keys correctly. (Control + "i" generates Ctrl-C.)

I believe the problem is in the package gnome-control-center 1:2.22.1-0ubuntu4.1

Steps to reproduce:
1. From the keyoard layout preferences dialog, select USA Dvorak.
2. In a terminal, confirm the Dvorak layout for normal text entry.
3. In the terminal, type Ctrl-c (using the "I" key) and get a tab; type Ctrl-j (using the "C" key) and get a ctrl-c.


Actual results:
Ctrl-c (the "I" key) produces ctrl-i (a tab).

Expected results:
Ctrl-c (the "I" key on a Qwerty keyboard) should produce a break.

Does this happen every time?
Yes

Other information:
Comment 1 Christian Persch 2008-08-12 18:50:34 UTC
Most likely a dup of bug 162726.
Comment 2 Tommy McGuire 2008-08-12 21:18:05 UTC
Yep, it looks like it is.

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