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 648919 - Region and Language is wrong place for ctrl key position preference
Region and Language is wrong place for ctrl key position preference
Status: RESOLVED DUPLICATE of bug 654617
Product: gnome-control-center
Classification: Core
Component: Region & Language
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-04-29 05:41 UTC by jlquinn
Modified: 2011-07-15 13:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jlquinn 2011-04-29 05:41:44 UTC 
Debian testing x86_64, gnome-control-center 3.0.0.1-1

I just upgraded from gnome 2.30 to gnome 3.0 and found that my capslock key was no longer acting like a control key.  I went looking for the configuration parameter and spent quite a while finding where it had gone.

Region and Language -> Layouts -> Options -> Ctrl key position

This was *VERY* non-intuitive to me.  The location of the control key has nothing whatsoever to do with regional or language-specific preferences.  This setting really belongs somewhere under the keyboard options.  This totally seems like a regression.

I'd make the same argument for the key sequence to kill the X server, caps lock behavior, Alt/Win behavior, etc.  The majority of settings here have nothing to do regional or language-related issues.

Perhaps the simplest would be to make these options reachable through both Region and Language preferences and Keyboard preferences.
Comment 1 Bastien Nocera 2011-07-15 13:00:27 UTC 
We'll be removing the dialogue altogether actually, and letting tweak configurators handle those types of settings.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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