Bug 84560 - FILEOPEN: Libreoffice silently ignores errors when creating the lockfile
Summary: FILEOPEN: Libreoffice silently ignores errors when creating the lockfile
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: File-Lock WebDAV
  Show dependency treegraph
Reported: 2014-10-01 17:05 UTC by FrOutlook
Modified: 2024-02-17 03:13 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description FrOutlook 2014-10-01 17:05:15 UTC
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.
Comment 1 Jan 2015-02-24 17:35:58 UTC
I can verify this behaviour ( 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
Comment 2 Robinson Tryon (qubit) 2015-03-05 20:13:58 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2016-09-20 10:18:14 UTC Comment hidden (obsolete)
Comment 4 Aron Budea 2018-04-17 23:03:00 UTC
This is not a critical issue, adjusting importance accordingly.
Comment 5 qa-admin@libreoffice.org 2020-02-16 20:52:01 UTC Comment hidden (spam)
Comment 6 QA Administrators 2022-02-16 03:35:35 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2024-02-17 03:13:11 UTC
Dear FrOutlook,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team