After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 117846 - On Login get NFS Lock error
On Login get NFS Lock error
Status: RESOLVED DUPLICATE of bug 84101
Product: GConf
Classification: Deprecated
Component: XML backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GConf Maintainers
Trevor Curtis
Depends on:
Blocks:
 
 
Reported: 2003-07-19 15:28 UTC by Chris Lee
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description Chris Lee 2003-07-19 15:28:23 UTC 
Not sure if this is GDM or some other component.
When I log in on a second machine I get an NFS Lock error and get chucked out.
This also happens when I have a client fall over, but that is another issue.

It would be far better to get a "this is a read only session - you can not
change your settings" message, so I can still do things only not change any
settings.
Comment 1 George Lebl 2003-07-21 18:58:20 UTC 
Do you know where the lock error comes frome?  what is being locked?
Comment 2 Chris Lee 2003-07-22 09:23:28 UTC 
---ERROR MESSAGE---
Please Contact your Sys admin to resolve the following problem:
Could not resolve the address "xml:readwrite:/home/cslee/.gconf" in
the configuration file "/etc/gconf/2/path": Faild to lock
'/home/cslee/.gconf/%gconf-xml-backend.lock/ior': probably another
process has the lock, or your operating system has NFS file locking
misconfigured (resource temporarily unavailable)
---END ERROR MESAGE---
Hope this helps.

When I then press the button I am dropped from the session like a tone
of bricks.
Comment 3 George Lebl 2003-07-26 00:16:01 UTC 
This seems like a GConf bug (or in fact a problem for GConf)  If it
cannot lock the files it is unlikely to work even only as readonly
since what would happen if something else is actually changing the
gconf database.  I'm changing the module of this bug to GConf and
ccing havoc
Comment 4 Havoc Pennington 2003-07-28 00:24:54 UTC 
www.gnome.org/projects/gconf/ has some suggestions on how to work
around this.
Comment 5 Havoc Pennington 2003-10-22 20:13:29 UTC 

*** This bug has been marked as a duplicate of 84101 ***