Apache OpenOffice (AOO) Bugzilla – Issue 80279
[Samba] Opening .doc files in Writer causes directory lock on SMB share
Last modified: 2023-02-06 17:17:32 UTC
Using OO 2.2.1 Novell edition (build 2.2.0.2), openSuse 10.2, KDE 3.5.7, cifs.mount. The problem arises while opening .doc files created in MS Office from CIFS mounts. Until such a file is closed, no KDE application could access its directory (even read directory contents). How to reproduce: 1. Create a couple of .doc files in Microsoft Word and save them to \\server\share\docs\ as myfile1.doc and myfile2.doc (CIFS server is MS Windows 2003 SBS). 2. Mount "//server/share" to "/mnt/share" 3. Open the file "/mnt/share/docs/myfile1.doc" in OO writer. 4. Try opening "/mnt/share/docs" in Konqueror. Konqueror stops responding. 5. Try opening "/mnt/share/docs/myfile2.doc" in another OO Writer window. New window opens and stops responding. 6. Try saving opened "myfile1.doc" as another file while "Options->OpenOffice.org->General->use OpenOffice.org dialogs" is disabled. Konqueror-style dialog opens and stops responding. OpenOffice.org dialogs works well. 7. Try opening myfile1.doc in Microsoft Word from some Windows machine. It causes error ("cannot access..."). 8. Kill Konqueror dialog, close "myfile1.doc". Konqueror unfreezes. New OO Writer window unfreezes. Important observations: 1. No such problem with native OpenOffice documents. 2. No such problem with .doc files created by OO (even after further open-change-savings with Microsoft Word). However, these documents still cannot be opened by MS Word in read-only mode while opened for modification in OO. "cannot access..." etc. 3. OpenOffice Calc is not affected at all. So it seems that the problem lies somewhere in the Word import plugin that locks imported file from reading. Maybe it is a combination with some CIFS and KDE bugs, don't know. Possible workarounds: 1. Convert all documents to native OO format. 2. Open all documents with OO and save to the same .doc format using "save as" (just saving don't do the trick). 3. Disable file locking in soffice script: # SAL_ENABLE_FILE_LOCKING=1 # export SAL_ENABLE_FILE_LOCKING (downsides like possible data loss are quite clear). 4. Maybe using samba server instead of Microsoft Windows 2003 as SMB/CIFS server will help, I didn't try because it's not possible in my corporate network for now.
Created attachment 47260 [details] An example of file causing error
Created attachment 47261 [details] An example of file not causing error (created by OO Writer, not MS Word)
Framework issue.
TM->CMC: please have a look, thanks !
cmc->kendy: want to have a look at this, it's your distro and kde (not sure if that will be really relevant)
Anyone having a MS Windows 2003 SBS server around? Otherwise I suggest closing this issue. I expect not much activity from community for this issue since reproducing the issue involves getting access to proprietary software, which is not available for free download (at least i guess so for this product).
dobsche2, I doubt it is relevant that the SMB server is a Windows 2003 SBS one.
All these versions (Windows, Samba and OOo) are out-of-date now.