I set up a WebDAV share on my Windows 7 computer 64 bits service pack 1.
But there is no space available on this share.
When I open a file test.odt, the lock file is not created because the share
is full. The WebDAV server sends 507 code but no warning message is displayed to user.
Moreover, when I try to save file modifications, no error messages is displayed
and Libreoffice Writer is as if everything went well.
I can verify this behaviour (220.127.116.11) It is not WebDAV related. I have seen similar things on Samba Shares (e.g. on gvfsd-fuse on Ubuntu). Libreoffice seems to ignore all errors when creating/opening the lockfile.
Steps to reproduce:
1. Save a file as test.ods in /tmp
2. touch /tmp/.~lock.test.ods#
3. chmod 000 /tmp/.~lock.test.ods#
4. Open /tmp/test.ods -> LO will not complain about the broken lock and open/save the document
(This is an automated message.)
LibreOffice development currently prioritizes bugs with the so
called MAB (most annoying bugs). As this bug has not run
through that process (including writing a short rationale for
this bug being a candidate and other who are watching the
tracker bug silently approving that rationale etc), its priority
is set to high. Note this is effectively no change in the
urgency assigned to this bug, as we are currently not making a
difference between high and highest and severity is untouched.
You can find out more about MABs and how the process works by
contacting the QA Team on IRC:
The QA wiki page also gives you hints on how to get in contact
with the team (if IRC fails you, your next best choice is the
** 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)
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!
This is not a critical issue, adjusting importance accordingly.