GNOME Bugzilla – Bug 106867
NFS Locking problem in HOME
Last modified: 2004-12-22 21:47:04 UTC
If gconf cannot put a lock in $HOME, then the desktop is not started. This is a problem when the $HOME directory is NFS mounted from a different client which does not run statd/lockd. The lock daemons have had a number of security and other issues, so running them is not necessarily desired; even if run, version issues frequently prevent them from working correctly. An option to Gnome to avoid locking (assuming only one login/user at a time) would solve the problem. Currently we cannot use the more recent release (through RedHat) of Gnome, as it will refuse to lay out a (single) desktop.
See http://www.gnome.org/projects/gconf/ which discusses the issue in some detail and mentions the GCONF_LOCAL_LOCKS=1 workaround.
*** This bug has been marked as a duplicate of 84101 ***