From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
After installing RH 8 on first bootup and all subsequent reboots, the GNOME
login window is replaced with the X window login and the following message is
displayed after login:
"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:
Failed to activate 'OAFIID:GNOME_SettingsDaemon
GNOME will still try to restart the Settings Daemon next time you log in."
This prevents various desktop settings and functions from being accessed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RH 8 (default settings for GNOME)
2. Boot Machine
3. Log in
Actual Results: Error message is displayed (see bug description)
Expected Results: The GNOME Daemon should start without any problem as no
configuration files were changed.
This only happens to a small number of people. If you have any ideas
how your hardware or configuration may be unique, please advise.
Niall's machine, received via email:
PC Model: HP Kayak XAs
Processer: PIII 800MhZ
Memory: 512 MB
Disk: SCSI Quantum 8 GB
Video: 64MB ATI Radeon
CD: Generic brand 24x
Can you try "rpm -Va" and attach the output? (and reopen bug)
Created attachment 90487 [details]
Output of rpm --root /usr/client/xstation2/ -q -a
Done from NFS server of affected machine
Happens to me too.
I didn't do a standard install because I couldn't work out how to do that on a
diskless machine (root is NFS - significant?) so perhaps I am missing an RPM (I
didn't use -force to install anything AFAIR). Alternatively perhaps this happens
because I can't shut down normally with an NFS root, so I just pull the plug.
Since there are no local filesystems this should be OK, but...
Forgot to mention. Mine's a VIA C3 Ezra with 800MHz and it was a new RH8.0
installation, not an upgrade.
Installed control-center, now the error is gone.
A dependency is missing I think
*** This bug has been marked as a duplicate of 100562 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.