Opening Yast Gnome Errors.

Hey guys -

I have no idea what’s going on…

When I attempt to open yast2 in suse 11.1 I get an error that states.

“An error occurred while loading or saving configuration information for y2controlcenter-gnome. Some of your configuration settings may not work properly.”

In the details box it states…

“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.)
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.)
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.)
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.)
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.)”

Any ideas?

I’ve seen something similar to this when the /tmp directory has been cleaned out. The fix for me was just a reboot.

Cleaned out /tmp and /var/tmp, no luck.

Anyone have anything else?

> Anyone have anything else?

you can TRY this, it uses zypper to fix yast:

open a terminal, then type the first line below and press enter, then
give your root password when asked…then type the second line and
WAIT until all activity has stopped and you are returned to the
command prompt (it may take a long time to find and fix all the
problems), and then type the third line, wait, repeat


su -

rpmdb --rebuilddb

zypper ref

zypper up

After that try YaST again.


natural_pilot