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 229063 - Failed to get lock using fcntrl(2) Permission denied
Failed to get lock using fcntrl(2) Permission denied
Status: RESOLVED DUPLICATE of bug 205095
Product: evolution
Classification: Applications
Component: Do Not Use
pre-1.5 (obsolete)
Other All
: Normal blocker
: ---
Assigned To: JP Rosevear
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-08-16 19:44 UTC by Edward Croft
Modified: 2013-09-13 12:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Edward Croft 2002-08-16 19:44:43 UTC
Please fill in this template when reporting a bug, unless you know what 
you are doing.
Description of Problem:

Received the following error:
Error while storing folder 'tmp/home/ecroft/evolution/local/Inbox'
Failed to get lock using fcntrl(2): Permission Denied.

We are using NIS and NFS for home directories rather than on local 
machines. We are running Red Hat version 7.3, and Evolution 1.0.8. We 
connect to an Exchange 5.5 server using IMAP.

Steps to reproduce the problem:
1. Install latest Evolution on Red Hat 7.3
2. Use NIS to mount home directories on NFS shares. 
3. Set IMAP connection to Exchange server. 

Actual Results:


Expected Results:


How often does this happen? 


Additional Information:
Comment 1 Gerardo Marin 2002-08-16 19:55:08 UTC

*** This bug has been marked as a duplicate of 205095 ***
Comment 2 Edward Croft 2002-08-16 20:04:16 UTC
 I have gotten it to download the folders and then after a bit we  
get that error and you can't even restart Evolution after that. It  
stops downloading email after that error. You can close down  
Evolution, but when you restart it gets to the last icon and the  
splash screen goes, there is a box that blips up in the corner as if  
it was going to post an error, but that goes away.   
I was wondering if this could be a timeout error while trying to get  
a lock from the NFS share.