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 314625 - dialog for selecting X vs Gnome keyboard configuration not precise enougth
dialog for selecting X vs Gnome keyboard configuration not precise enougth
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.8.x
Other All
: Normal minor
: ---
Assigned To: Sergey V. Udaltsov
Control-Center Maintainers
: 351020 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-08-26 22:54 UTC by Alexandre Garel
Modified: 2006-09-28 00:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Alexandre Garel 2005-08-26 22:54:16 UTC 
At the start of Gnome, if X keyboard settings are not the same as Gnome's ones I
got the following message in a dialog :
"the X system keyboard setting differ from your current Gnome keyboard settings.
Which set would you like to use ?"
It's not easy to make a choice as no other info is given.
Could the dialog tells the keyboard layout for each configuration. Eg :
"the X system keyboard setting (fr) differ from your current Gnome keyboard
settings (en). Which set would you like to use ?"

Other information:
not sure if I'am submitting bug to the right application, please redirect if
necessary.
Comment 1 Sergey V. Udaltsov 2005-08-27 00:44:35 UTC 
Well, it is the right place. The are two issues:

1. The 'diff' can be rather large. There can be different models, layouts (up to
4), options (unlimited number, in theory). Should user be presented with all
this clutter?

2. Well, there is some hassle calculating this diff - but in theory it is
doable. Sure not for 2.12
Comment 2 Sergey V. Udaltsov 2006-07-08 22:10:54 UTC 
IIRC now this information is presented in the dialog, so closing this one
Comment 3 Elijah Newren 2006-09-28 00:37:29 UTC 
*** Bug 351020 has been marked as a duplicate of this bug. ***