GNOME Settings_Daemon problem
I receive an error message while trying to login into the JDS3 Desktop.
GNOME Error: Could not initialize the GNOME Settings_Daemon.
As a result, the themes, backgrounds do not work correctly.
Is this a configuration or a hardware problem?
My system specs:
Intel P4 2.83GHz
RAM 640 MB
Intel 82845 gv/gm graphics controller
Realtek AC 97 Audio controller
OS: Solaris 10 1/06 for x86 (I installed only the first 2 CDs)
Can someone help me out with this?
[525 byte] By [
shibam] at [2007-11-26 6:42:06]
# 1
This can sometimes happen if your IP address has changed since your last login, as GNOME caches your IP address for some things and doesn't always correctly handle the change.
If the settings daemon error is the only one you're getting, you can often start it manually by running /usr/lib/gnome-settings/daemon in a terminal.
If that doesn't work, next thing to try would be killing any gconf* processes, clearing out any files in /var/tmp that include your username, and restarting JDS.
calum at 2007-7-6 14:57:31 >
# 2
Sorry, your method did not work. /usr/lib/gnome_settings/daemon could not be found, at the same time I could not resolve the problem by ending gconf厖..
Therefore I am adding some more details of the error message-
Error:
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.
I also installed the CD no. 3 but the message reappears. Is it really a hardware problem or do I need to change some settings? Can someone help me out with this?
# 3
I have a similar problem on a SB 1500 running Solaris 10,
so I don't think you have a hardware
problem. Sometimes when logging into JDS 3 I get
the three pop-ups with the following error messages:
1.) There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work
correctly.
The GNOME Settings Daemon restarted too many times.
GNOME will still try to restart the settings Daemon next time you log in.
2.) Nautilus can't be used now, due to an unexpected error from Bonobo when
attempting to register the file manager view server.
3.) There was a problem registering the panel with bonobo-activation-server.
The error code is 3. The panel will now exit.
Pop-ups 2 and 3 reopen infinitely so I have to kill the whole XSession from
a remote workstation. However a user process
/usr/lib/bonobo-activation-server --ac-activate --ior-output-fd=24
remains alive and impedes a successful login into JDS next time. So this process must be
killed first.
# 4
In my experience, the usual culprit in these components startup issues is /var/tmp/orbit-<userid>, so I would suggest completely logging out, making no sure no user processes are left behind, removing (or renaming if you want to be very safe) this directory and trying to log back
