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 654617 - Remove the "Options" dialogue
Remove the "Options" dialogue
Status: RESOLVED DUPLICATE of bug 662489
Product: gnome-control-center
Classification: Core
Component: Region & Language
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 311672 648919 (view as bug list)
Depends on: 654616
Blocks:
 
 
Reported: 2011-07-14 13:50 UTC by Bastien Nocera
Modified: 2012-06-20 01:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2011-07-14 13:50:35 UTC 
We'd move the keyboard shortcut to change layouts to the keyboard panel, as per bug 654616. There doesn't look like there's anything worth salvaging here that shouldn't be in a tweak UI instead.
Comment 1 Bastien Nocera 2011-07-14 15:58:45 UTC 
*** Bug 311672 has been marked as a duplicate of this bug. ***
Comment 2 Bastien Nocera 2011-07-15 13:00:27 UTC 
*** Bug 648919 has been marked as a duplicate of this bug. ***
Comment 3 Sergey V. Udaltsov 2011-08-12 00:26:57 UTC 
How do you define "worth salvaging" in relation to the keyboard options?

Anyway, perhaps it does not make sense even to start discussing this bug till there is settlement around 654616 (which I am afraid is not resolvable without unacceptable over-simplification).
Comment 4 William Jon McCann 2012-05-04 20:42:49 UTC 
https://live.gnome.org/Design/SystemSettings/RegionAndLanguage#Input_sources
"The layouts tab currently has an additional Options dialog which contains a large number of advanced (and often confusing) settings. This will not feature in the new Input Sources panel. A subset of the options provided by that dialog are frequently used."
Comment 5 Matthias Clasen 2012-06-20 01:18:46 UTC 

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