You are not logged in.
Having some problems with the gnome-settings-daemon. Everything takes forever to start. And then I have to start the daemon manually. I can't even open anything in gnome. Every app just freezes for a long time when the gnome-open dialog is starting. Several other gtk stuff is behaving strangely. The errors I get when starting gnome :
An error occurred while loading or saving configuration information for gnome-session. Some of your configuration settings may not work properly.
Details : Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-4njxAH0Dyi: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-M1sc62XxCp: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-S8Csrxqt9U: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-fJlXX12kYH: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-3vn9gjIRC8: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-cuVx9dwVJi: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-2BvEFY3AVm: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-wktJNFGpCv: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-ItPkj52T5M: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-VHDMGJQU3K: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-eI7kB8BYdo: Connection refused)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-sF1bxSAuxY: Connection refused)
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
The last error message was:
Failed to connect to socket /tmp/dbus-9eQSZ0qQmY: Connection refused
GNOME will still try to restart the Settings Daemon next time you log in.
Offline
Are you using the gnome packages from testing? gnome-settings daemon for 2.24 isn't in there yet. It's likely the change to policykit broke the old settings-daemon.
Offline
I'm having this problem too. I am running testing. Thanks, Megamixman for explaining. I will wait to see how the new version of gnome-settings daemon does.
Offline
me 3 on this... gedit is the worst.
Offline
Hi,
I solved this doing
useradd policykit
then restarting dbus.
Now Gnome runs correct, but when I try to open something about gnome-appearance-properties, I have a slightly different error.
It says that Gnome Settings Daemon isn't running, but it's listed in processes by ps aux!
Anyone with the same problem?
Sorry for my english.
Bye,
Damym
Offline
In case you added the policykit user, delete it again.
then:
groupadd policykit
pacman -S policykit
This should reinstall policykit, create the correct user account, assign it to the policykit group and fix permissions for all files in the policykit package.
I'll change the policykit package soon to get rid of the reserved gid that isn't reserved on most systems.
Offline
Sorry, forgot to say I did a reinstall. But maybe someone else can benefit from the thread.
Offline
I'm having similar errors, but the system seems to be working mostly fine. No delays anyway.
On gksu gedit I get a lot of :
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.).
And I can't setup preferences because it's all greyed out.
This does not happen on running gedit as current user.
Is this related to me running gedit 2.24?
I tried adding policykit group and "#pacman -S gnome-settings-daemon policykit", but none of it helped.
/var/log/messages says nothing about any error.
Where did you find that 2nd code rocknrolf77?
Any solution?
Offline
Looks like this has to do with gnome 2.24,
a bug have been filed here:
Offline
For me gedit freezes upon start for a minute then it is usuable (running Arch 686, GNOME 2.24).
Regards
André
Offline
I get the same error when try to become administrator in gnome print manager.
An error occurred while loading or saving configuration information for gnome-cups-manager.
Some of your configuration settings may not work properly.
Last edited by mahan_h (2009-03-24 12:30:36)
Offline
Mahan_h, have you solved this problem? I get the same error.
Offline
I get this as well when trying to add a new printer... All my former printers are now non accessible.
"An error occurred while loading or saving configuration information for gnome-cups-add. Some of your configuration settings may not work properly."
Offline
I am getting this error and I don't even use gnome. I have openbox and I get this error when I try to open firefox , thunderbird, terminator and sever other apps. They then either freeze or crash except for terminator which seems to work if the error message is dismissed.
Has someone found a fix yet?
Offline
I am getting this error and I don't even use gnome. I have openbox and I get this error when I try to open firefox , thunderbird, terminator and sever other apps. They then either freeze or crash except for terminator which seems to work if the error message is dismissed.
Has someone found a fix yet?
I get the same error with openbox
Offline