Bug 133343 - Gnome settings daemon error
Gnome settings daemon error
Product: Fedora
Classification: Fedora
Component: control-center (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jonathan Blandford
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-09-23 07:22 EDT by Srini
Modified: 2013-04-02 00:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-24 23:58:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Srini 2004-09-23 07:22:19 EDT
Description of problem:
After the latest yum update (did it on 2oth Sep, I think gtk etc was 
updated), when I login to a gnome desktop (of an existing FC2 
installation) the panel is not displayed properly and this message is 

There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not 
work correctly.
The Settings Daemon restarted too many times.
The last error message was:
Child process did not give an error message, unknown failure occurred
GNOME will still try to restart the Settings Daemon next time you log

The message does not go away even after reboot.  It happened for all 
users.  new users were also affected

Version-Release number of selected component (if applicable):

How reproducible:
Looks to be update of some other modules
Comment 1 Jonathan Blandford 2004-09-23 12:00:28 EDT
If your machine is still in this state, can you log in in failsafe
mode, and start /usr/libexec/gnome-settings-daemon, and see if it is
crashing.  If so, can you get a backtrace?
Comment 2 Jonathan Blandford 2004-09-23 12:02:36 EDT
(If you need more information about getting a backtrace, there's some

Comment 3 Srini 2004-09-24 23:58:35 EDT
Updated to the latest GTK via up2date and the problem has 

Thanks & Regards

Note You need to log in before you can comment on or make changes to this bug.