Red Hat Bugzilla – Bug 183607
gnome-keyboard-properties resets GTK theme to Clearlooks
Last modified: 2007-11-30 17:11:25 EST
Description of problem:
Manipulating the keyboard layout settings resets the "GTK" theme to
"Clearlooks" when it used to be "Bluecurve"!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Execute "gnome-keyboard-properties".
2. Play around with the layout scheme settings.
"GTK" theme gets reset to "Clearlooks".
"GTK" theme shouldn't have been altered.
hmm, doesn't happen here. Can you describe your "playing around" in more detail ?
What version of xorg-x11-xkbdata do you have ?
I wonder if settings daemon is crashing...
To reverify the issue once again, I execute the following steps using
the mouse solely, not the keyboard:
1. Remove all dot directories (.gnome2, ..) in my account to reset them
to factory defaults.
2. Upon log-in, set "GTK" theme to "Bluecurve". Works.
3. Launch "gnome-keyboard-properties".
4. Go to "Layouts" (Keyboard model: "Generic 105-key (Intl) PC",
Scheme: "German Eliminate dead keys").
5. Click "Add..."
6. Select "U.S. English layout".
7. Confirm ("OK").
Bingo! The theme switches instantaneously to "Clearlooks". Reopen
"gnome-theme-manager", and see the theme switch back to "Bluecurve"
wich is still selected there. Version of "xorg-x11-xkbdata" is 1.0.1-6
which is the latest one. Without yesterday's "xorg-x11-xkbdata" mess,
I would have probably never noticed this one!
Bug still present in "control-center-2.14.0-1". I checked with the
live CD of another distro that the issue is not Fedora specific.
It occurs there, too.
what if you upgrade to the libxklavier in rawhide?
I installed the system from scratch yesterday (rawhide 03/14/06).
Todays updates were obviously also installed, thus including
"control-center-2.14.0-1" as stated in commet #4. Anything else
to update to?
No that should have everything (assuming you have libxklavier-18.104.22.1686.02.23-2).
I'm fairly sure this is a duplicate of bug 183569, but it could be the
workaround added to libxklavier to help address that bug doesn't actually work
around all the problem cases.
*** This bug has been marked as a duplicate of 183569 ***