Heinz Diehl wrote:
Hi,
after a system crash, yast2 throws the following on me:
** (y2controlcenter-gnome:7997): WARNING **: error accessing /desktop/gnome/applications/y2cc-gnome/cc_actions_list [Failed to contact configuration server; som e 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.)]
The "system" menue after clicking on the "computer" button in Gnome has also disappeared.
I have read a bunch of articles, but was not able to solve the problem. I did also kill /tmp/* and similar files, and have cleaned ~/.gconfd without any success.
Does anybody have an idea where these lockfiles are?
The document to which you posted a link says: I'm having a lock file problem. What do I do? Usually a problem here involves either NFS, or a kernel bug. The per-user daemon locks two files in the default configuration: ~/.gconfd/lock/ior ~/.gconf/%gconf-xml-backend.lock/ior You mentioned checking ~/.gconfd but did you also check ~/.gconf ? Also which user is logged in and which user is running yast and did you check both users' directories? Just a wild idea.
Thanks, Heinz.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org