GNOME Bugzilla – Bug 121217
wrong permissions on gconf directories makes things go boom
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: GNOME is crashed totally. .xsession-errors reads: 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: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory) 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: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory) 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: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory) 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: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory) 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: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/root/.gconfd/lock/ior' not opened successfully, no gconfd located: No such file or directory) I am not running NFS. Steps to reproduce the problem: 1. GNOME crashed totally, I can't restart 2. 3. Actual Results: Expected Results: How often does this happen? Additional Information:
Try "strace -o /tmp/output -f gconf-sanity-check-2" in a console and see what's in /tmp/output (perhaps attach that file)
Hi, It's crashed last week. Till now I could n't able recover. If I login on GNOME desktop, the desktop freezes with incomplete windows. Thanks
Created attachment 19704 [details] Output of /usr/bin/strace -o /tmp/output /usr/libexec/gconf-sanity-check-2
How about "strace -f -o /tmp/output gconfd-2"?
Created attachment 19712 [details] Output of /usr/bin/strace -o /tmp/output2 /usr/libexec/gconfd-2
The end of that strace shows a couple messages going to syslog - can you look at /var/log/messages and see what those were?
Hi Havoc, I checked the /var/log/messages, found that errors are due to wrong permissions to .gconfd directories for all the logins. I changed those to 700 and run the strace again, problem is fixed. Could you able to tell me why permissions on .gconfd directory for all the users got changed. Thanks
No, I can't explain that. What OS and kernel version are you running? what is the output of "umask"?
I can confirm this on RHL 9 if .gconf or .gconfd has g+w or x/s set then gconfd bails w/o a terribly useful error message.
Redhat 9, kernel ver. 2.4.20-20.9 umask - 0022
Created attachment 21136 [details] gconf permissions can be critical with userdel/useradd too.
See also bug #141138
The ORBit code to handle its /tmp/orbit-username stuff is in ORBit2/src/orb/GIOP/giop.c:giop_tmpdir_init(). We should use something similar for GConf.
*** This bug has been marked as a duplicate of 141138 ***