Red Hat Bugzilla – Bug 158244
There was an error starting the GONME Settings Daemon
Last modified: 2008-05-01 11:38:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922
Description of problem:
After rebooting the machine, every user login gets the folloing error:
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not
The Settings Daemon restarted too many times.
GNOME will still try to restart the Settings Daemon next time you log in.
which is followed by 4 more errors related to GNOME applets:
The panel encountered a problem while loading "OAFIID: GNOME_xxxApplet" unknown CORBA exception id IDL:omg.org/CORBA/INV_OBJREF:1.0
where xxx is Pager, TaskList, SystemTray, and Clock. This results in several items not being available for utilization by users -- including root.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL
2. Login and see that everything is fine
4. Login and see that GNOME Settings Daemon cannot start
Actual Results: See description
Expected Results: The GNOME desktop starts, the system tray has a clock, workspace control is available, No errors are reported that the GNOME Settings Daemon cannot start, etc...
Computer Model: HP Compaq dc7100 CMT
Processor: Intel Pentium 4 with Hyper-Therading @ 3.2-GHz
BIOS: HP 786C1 v01.05, 6/16/2004
Chipset: Intel 915 G chipset
Hard Disk Controller: 40 - 160-GN, 7200-rpm Serial ATA/100
Hard Drive: 80-GB SATA @ 7200-rpm (Western Digital)
Network Card: Broadcom NetExtreme Gigabit Ethernet
Graphics Card: nVIDIA GeForce 6600 GT with 128-MB RAM
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.