Apache OpenOffice (AOO) Bugzilla – Issue 101282
OOo 3.0 cannot save to network drive
Last modified: 2013-01-29 21:51:58 UTC
Whenever saving documents from writer or calc to a SAMBA share, it creates the lock file and then claims that another user has locked the file. This happens when creating new files - it then does create the file and create the lock file but if press save a second time then it will refuse to do so because it thinks it is locked. If you open an existing file then it just refuses to save. I'm pretty surprised I couldn't find this documented here already, and I did look. If this is a duplicate report then my apologies. This is well documented on various user forums but it seems that no bug has been filed because I can't find one. Here is a good thread on the subject: http://user.services.openoffice.org/en/forum/viewtopic.php?f=6&t=11255&st=0&sk=t&sd Note the thread above claims it is solved, but not really. They recommend remounting the filesystem with different options to defeat the locking mechanism. In 3.0, OO changed its file locking method and that caused it to stop working with SAMBA shares. I have used OO 1.0 and 2.0 and 3.0 in the same network environment, and as soon as I started using 3.0 this problem existed. Other users report the same issue when using OO on XP or Ubuntu. I am a Mandriva desktop user. The common thread is a SAMBA network share.
Same problem with Samba Share over Sitecom LN350 NAS. Various computers get "General I/O Error" saving Calc to server, sometimes opening files too - then they are corrupt and nothing can save them.
grantsv, I think you have identified another issue. Corrupted files are not part of the problem with SAMBA shares. The files remain intact, but OO's new locking algorithm doesn't work on SAMBA unless you do some crazy workarounds on SAMBA to trick it.
which filesystem do you use on your samba share? It seems for me to have the same causes as http://qa.openoffice.org/issues/show_bug.cgi?id=84431
84431 does sound very similar in behaviour. I am not using nfsmount or FAT though. It is SAMBA with a shared ext3 filesystem. Clients running OO 3.0 on Windows OR Linux have the problem. OO 2.x does not have the problem. 88431 states that the file still gets saved. This only happens for me when creating new files, not when trying to re-save existing files. Again, this problem only happens with OO 3.0, not with OO 2.x.
Same issue using Vantec Nexstar LX NAS box. Only happens with OOo 3.x Even with the following mount options it's a no go: mount -t cifs -o uid=1001,gid=101,password=,nobrl,_netdev,noexec,user,rw,nounix
I'm having this issue as well. Win XP SP2 [Version 5.1.2600] going against a samba server on Red Hat linux. I can save to any file name the first time. Then OO creates a lock file in the same directory as the file that I just saved. In order to re-save the OO Writer file, I have to first delete the OO lock file. Here's the error message: "Error saving the document Parts Look-up links: Object not accessible. The object cannot be accessed due to insufficient user rights." Somehow, OO must not be granting itself the proper rights to access its own lock file. Please note: the lock file is not removed from the network drive either when I exit the OO document or when I exit the OO writer application. The lock file _is_removed from the local drive/directory when I close the document. Note: saving works just fine to my local hard drive. If you need more detailed information, please let me know.
Sorry - Forgot to mention this is OO 3.1.0 build 9399.
We have similar issues, pls see my report (No.106623). Below is our issue description: Our filesystem of shared network driver is netapp. Exported to windows PCs in network using CIFS. Exported to Unix PCs (Solaris, Linux) using NFS. File permissions are controlled by windows AD controller. Using windows, OpenOffice-files can be created and edited on a shared network driver. If an OpenOffice file is already opened by another windows-user, it will be opened as copy or read-only. Everything works fine. Using Unix (Linux, Solaris), OpenOffice-files can not be saved on this shared network drive(CIFS based). Existing files will always be opened as read-only. New files can not be saved: File-->Save-->... results in "Error saving the document Untitle1: Object not accessible. The object cannot be accessed due to insufficient user rights", even if the file does not yet exist. Files can be saved on a local directory and then copied (using cp) to the network directory. Problems occur only with Openoffice files, other programs are not affected (tested with nedit).
today we found a new issue of openoffice. 1 the openoffice is installed in local. If open a ppt file, it will be slow, and if there are some tables which also created by MS-office in the ppt file, it will be slower. No matter it is under unix or windows. 2 the openoffice is installed on the server which is unix environment. if open a ppt file and there are some tables which created by MS-office in it, the openoffice would always crash when we edit the ppt file. did you encounter this issue? could some of you give us some hints? thanks
zxdnju, I think your problem is unrelated. If you're looking for help then you need to find the forums, but if you're reporting a bug in OO then you should create a new entry somewhere in this system. The problem you're describing is different than the one in this thread.
*** Issue 101282 has been confirmed by votes. ***
I have the same problem - i can open file from samba share, but can not save, file locking. Ms office, Koffice work fine.
remove my CC because I don't use a samba share any more.
*** Issue 112966 has been marked as a duplicate of this issue. ***
*** Issue 113653 has been marked as a duplicate of this issue. ***
Similar issue here. Mounted SAMBA share. I can save a new file to the share fine, but I cannot save any changes. It just gives a "General input/output error while accessing" message. Using OpenOffice Calc 3.2.1.4 on a Linux 2.6.32 kernel.
I discovered a workaround for this issue. Refer to this post: http://ubuntuforums.org/showpost.php?p=6012786&postcount=691 In summary, I needed to disable byte range locks on the cifs share. This works around the problem of openoffice not properly implementing cifs style byte range locks. The "nobrl" cifs mount option did the trick.