GNOME reports GConf Error when logging in
This document (3143431) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Desktop 10
SUSE Linux Enterprise Server 10
Situation
When logging in into a GNOME session the following error message appears:
ERROR: 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 convert IOR '' to an object reference 2: Failed to convert IOR '' to an object reference)
In/var/log/messagesthe following error message appears:
ERROR: Mar 17 07:37:11 SERVER gconfd (root-27209): Failed to get lock for daemon, exiting: Failed to lock './gconfd-root/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
This problem also affects newly created users as well as the root user.
Resolution
This issue might be experienced if the environment variable TMPDIR is being set
- to a wrong path or
- to a path with improper permissions.
Please ensure the system uses/tmpas TMPDIR (which is the default). In case TMPDIR needs to point to a different directory ensure the permissions are set accordingly (chmod 1777 if shared with other users) on the new destination.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3143431
- Creation Date: 02-Apr-2008
- Modified Date:22-Feb-2021
-
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Real Time
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
