Description of problem:
When logging on to Gnome in FC2 on an x86_64, it gives an error
message (given below) and either exists or continues without nautilus
displaying the icons
"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.
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 in."
This happens every time I try to log in.
Tried with a fresh install as well as with updates...no go.
The only thing I might be able to think of is the nvsound and nvidia
drivers which are installed.
Steps to Reproduce:
1. Log in as any user on FC2
It either gets stuck at gnome-panel or continues past giving the error
message quoted above....but no icons displayed on the desktop....or
improper icons displayed.
KDE however does not crash on this system.
Tested and working workaround is : rm -Rf /tmp/orbit-$USER
Huh? How could that workaround work? Is this an old user home
directory? Can you log in in fail safe mode, run gnome-session, and
attach any obvious errors in the logs?
I found this page while googling for an answer to my problem, which
is exactly the same as your's. To me it occurred while starting a VNC
session. This resolved my problem, I can log in to the gnome desktop
again now, without any errors and with all my settings correct.
But to be honest I am kinda new to bugzilla-protocol (and linux as a
whole for that matter). Just thought I'd post this here to help you
out. I could have misinterpreted this bug, the use of bugzilla, or
misposted this comment. In that case, sorry.. In case you want more
info, please tell me what exactly, cause I want to help out/learn.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
This bug is being closed because it has been in the NEEDINFO state for a long
time now. Feel free to reopen the bug report if the problem still happens for
you and you can provide any information that was requested.