Red Hat Bugzilla – Bug 192051
gnome-keyboard-properties have "corrupted" gnome-settings-daemon which seems to effect bonobo
Last modified: 2008-03-18 14:34:14 EDT
Description of problem:
Please re-set component if incorrect: couldn't find gnome-keyboard-properties or
gnome-settings-daemon component to file under - may be bonobo too?
Gnome Keyboard Preference's configuration gui causes the Gnome Theme to cycle
between chosen theme and the default fc5 theme. Also, the Keyboard Preferences'
Layout Options' "Alt/Win key behaviour" doesn't seem to be honoured (i.e. Supper
doesn't appear mapped to Win-keys as Window Preferences' Movement Key (Super)
Also, the Keyboard Preference's Typing Break has stoped working. Keyboard
switching hasn't worked since install (between Maori and US). And, Error
Messages (attached) have been appearing at logon as well as when Keyboard
Preference's gui is accessed.
Version-Release number of selected component (if applicable):
[morgan@morgansmachine ~]$ rpm -q gnome-session
Steps to Reproduce:
1.Open Desktop -> Preferences -> Keyboard
2.Screen starts cycleing between default and custom Theme & cpu goes to 100% (on
Failure to save settngs; cycling between Themes; error pop-ups
Set Keyboard preferences
Created attachment 129294 [details]
Error window pic
Created attachment 129295 [details]
Warning message pic
I'm experiencing similiar problems. It seems that preference caplets can't talk
to the gnome-settings-daemon even though it's running. Also some of my
preferences don't seem to be working like certain keyboard bindings. I haven't
really changed any preferences in quite a while and this is fairly new, within
the last week, so I don't necessarily believe any one preference is corrupted.
More like the gnome-sessions-daemon is locking up or something.
Changed component to gconfd-2.
version of gconfd-2 (which this may be better loged against?):
[morgan@morgansmachine ~]$ rpm -q GConf2
I created a new login and moved everything across. A work-around, and a lot of
We no longer support Fedora Core 5 and I am currently trying to get my open bug
count down to a more manageable state. I'm going to close this bug as WONTFIX.
If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?
(this is a mass message)