System: Windows 7 Professional Version 6.1 (Build 7601: Service Pack 1) LibreOffice: Reproduced in both 3.3.1 and 3.3.2 If you open a file from a so-called "web folder", a linked webdav resource in windows, and try to save your changes back to the file, OpenOffice will fail saving it, and that actually renders the file useless subsequently. It works flawlessly in other programs, such as Microsoft Word, or if opened from the file dialog instead of from the explorer. The folder is password protected using Auth Digest. On saving the file, you will retrieve three error dialogs, two times access denied and then I/O error. The exact error messages: "Error saving the document Test: Access to \\dav....\DavWWWRoot\Test.odt was denied." and "Error saving the document Test: General Error. General input/output error." The bad thing is that afterwards the file is corrupt for all other programs as well. The webdav server (Apache 2 mod_dav in my case) reports: [Tue May 10 15:06:28 2011] [error] [client 127.0.0.1] Could not LOCK /Test.odt due to a failed precondition (e.g. other locks). [423, #0] [Tue May 10 15:06:28 2011] [error] [client 127.0.0.1] (2)No such file or directory: Existing lock(s) on the requested resource prevent an exclusive lock. [423, #0] Apparently, LibreOffice never releases the lock. This is confirmed by looking at the file properties with cadaver: dav:/> propget Test.odt Fetching properties for `Test.odt': Win32CreationTime = Tue, 10 May 2011 15:06:13 GMT Win32LastModifiedTime = Tue, 10 May 2011 15:06:26 GMT Win32LastAccessTime = Tue, 10 May 2011 15:06:26 GMT Win32FileAttributes = 00000020 resourcetype = creationdate = 2011-05-10T15:06:27Z getcontentlength = 0 getlastmodified = Tue, 10 May 2011 15:06:27 GMT getetag = "43009c-0-4cd7c2c0" executable = F supportedlock = <lockentry> <lockscope><exclusive></exclusive></lockscope> <locktype><write></write></locktype> </lockentry> <lockentry> <lockscope><shared></shared></lockscope> <locktype><write></write></locktype> </lockentry> lockdiscovery = <activelock> <locktype><write></write></locktype> <lockscope><exclusive></exclusive></lockscope> <depth>infinity</depth> <owner><href>username</href></owner><timeout>Second-3536</timeout> <locktoken> <href>opaquelocktoken:31370189-a889-4d76-8bc8-f214d6d804cd</href> </locktoken> </activelock> getcontenttype = application/vnd.oasis.opendocument.text Configuration of the WebDAV folder: <Directory /var/www/..../dav> Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny allow from all DAV on AuthType Digest AuthName "...." AuthDigestDomain / http://.../ AuthDigestProvider file AuthUserFile /var/www/..../dav.digest Require valid-user </Directory> Steps to reproduce: - Set up a webdav share as described e.g. here: http://www.howtoforge.com/how-to-set-up-webdav-with-apache2-on-centos-5.5 - copy an ODF file to this WebDAV folder and try saving some changes - Afterwards see if you can open it in any other program (or try deleting or renaming the file). Please note that it works okay, if you open the file from the LibreOffice file dialog. If you start with an empty Writer, open the file open dialog and enter the DAV URL, it asks correctly for the password and can save the file! If opened directly from explorer, it never asks for the password.
Now that I look at my report again, perhaps the problem is that the file is opened using that windows "mount point", as \\$server\DavWWWRoot\$filename instead of through the real URI. There must still be something special in LibreOffice, though, because that works in other programs such as Notepad++ without asking for the credentials. Microsoft Word asks seperately for authentication, though. Perhaps the fix could be to determine that the file is indeed lying in a webdav folder?
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
@Andre Gemuend: Please attach a sample document!
Created attachment 63775 [details] Example document The content of the file is completely irrelevant. This is just lipsum.
Created attachment 63776 [details] First error message (will be repeated once) This is the first error message that appears upon saving.
Created attachment 63777 [details] Second error message This is the second error message. No matter if you discard your changes afterwards, the file will be a 0-byte file entry that is forever locked on your webdav server.
Confirmed in 3.5 as shown in the screenshots.
Sorry, in LibreOffice 3.5.4.2 Build ID: 165a79a-7059095-e13bb37-fef39a4-9503d18 to be precise.
We confirm that this longstanding bug still occurs on LibreOffice 4.0.x (Windows)
Some additional logs on the server side (webdav alfresco). The webdav error is an '400 bad request' when trying to unlock 11:43:04,872 DEBUG [org.alfresco.webdav.protocol] Properties of the FileInfo[name=Nouveau Texte OpenDocument.odt, isFolder=false, nodeRef=workspace://Spac esStore/dbf16368-694b-4404-a440-c61f9dac2bfd] was changed 11:43:05,367 INFO [org.alfresco.webdav.protocol] LOCK took 568ms to execute [/alfresco/webdav/Espaces%20Utilisateurs/cpotter/Nouveau%20Texte%20OpenDocume nt.odt] 11:43:05,712 DEBUG [org.alfresco.webdav.protocol] WebDAV request UNLOCK on path /alfresco/webdav/Espaces%20Utilisateurs/cpotter/Nouveau%20Texte%20OpenDocu ment.odt 11:43:05,712 DEBUG [org.alfresco.webdav.protocol] Parsing Lock-Token header: opaquelocktoken:dbf16368-694b-4404-a440-c61f9dac2bfd:cpotter 11:43:05,712 DEBUG [org.alfresco.webdav.protocol] UNLOCK is returning status code: 400 11:43:05,712 INFO [org.alfresco.webdav.protocol] UNLOCK took 0ms to execute [/alfresco/webdav/Espaces%20Utilisateurs/cpotter/Nouveau%20Texte%20OpenDocume nt.odt] 11:43:05,930 DEBUG [org.alfresco.webdav.protocol] WebDAV request PROPFIND on path /alfresco/webdav/Espaces%20Utilisateurs/cpotter/Nouveau%20Texte%20OpenDo cument.odt 11:43:05,931 DEBUG [org.alfresco.webdav.protocol] Fetched node for path: servlet path: /webdav 11:43:05,932 INFO [org.alfresco.webdav.protocol] PROPFIND took 2ms to execute [/alfresco/webdav/Espaces%20Utilisateurs/cpotter/Nouveau%20Texte%20OpenDocu ment.odt] 11:43:06,154 DEBUG [org.alfresco.webdav.protocol] WebDAV request LOCK on path /alfresco/webdav/Espaces%20Utilisateurs/cpotter/Nouveau%20Texte%20OpenDocume nt.odt 11:43:06,154 DEBUG [org.alfresco.webdav.protocol] Parsing If header: null 11:43:06,154 DEBUG [org.alfresco.webdav.protocol] Timeout=3600, depth=-1 11:43:06,155 DEBUG [org.alfresco.webdav.protocol] Locking node: 11:43:06,156 DEBUG [org.alfresco.webdav.protocol] Fetched node for path: servlet path: /webdav 11:43:06,156 DEBUG [org.alfresco.webdav.protocol] LOCK is returning status code: 423 11:43:06,156 INFO [org.alfresco.webdav.protocol] LOCK took 2ms to execute [/alfresco/webdav/Espaces%20Utilisateurs/cpotter/Nouveau%20Texte%20OpenDocument .odt]
the UNLOCK request does not provide a valid LOCKTOKEN as described here https://tools.ietf.org/html/rfc2518#section-6.4 Logged via mod_dumpio: [Wed Feb 19 15:23:01 2014] [debug] mod_dumpio.c(74): mod_dumpio: dumpio_in (data-HEAP): Lock-Token: <645c1b74-adfc-4567-bb28-be263a80251f>\r\n I guess it shoud be : Lock-Token: <opaquelocktoken:645c1b74-adfc-4567-bb28-be263a80251f>
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Libreoffice: 4.4.5.2 on ubuntu 14.04 64bit The bug is still present. Error in webdav log: Could not LOCK /tst2.odt due to a failed precondition (e.g. other locks). [423, #0] [Sat Sep 12 09:52:10 2015] [error] [client 89.173.110.139] (2)No such file or directory: Existing lock(s) on the requested resource prevent an exclusive lock. [423, #0]
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
I guess this can be closed as duplicate of bug 96410 *** This bug has been marked as a duplicate of bug 96410 ***
Should it, really? This one was reported more than 4 and a half years earlier than 96410. Does it describe the same situation?