Created attachment 158752 [details] Combinations tested 1. Put a document on a Windows file share 2. Open that document on a Linux machine 3. Open the same document on a Windows machine (choose read-only in the dialog) 4. Try to save the document on Linux Result: Saving fails Expected: Saving should work, since Linux has exclusive write access to that document Note: This has something to do with system file locking. When disabling the option "UseDocumentSystemFileLocking" on the Windows machine, saving on Linux works fine. Attached the test protocol.
So a guess would be that when opening it read-only on Windows, LibreOffice doesn't use correct mode (read-only, shared) - see CreateFile's dwDesiredAccess and dwShareMode [1]. Note that from Windows share PoV, the file is not open from Linux side, it was atomically opened when read, then was closed, than will be attempted to open for writing later (IIUC the mechanics of Linux file operations). LO only detects the opened state using lock file. [1] https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilew
Hello Samuel, is this issue still reproducible with a master build ?
(In reply to Xisco Faulí from comment #2) > Hello Samuel, > is this issue still reproducible with a master build ? Setting to NEEDINFO
(In reply to Xisco Faulí from comment #2) > Hello Samuel, > is this issue still reproducible with a master build ? I would assume so, until someone proves the opposite. It has all info needed to reproduce, so not NEEDINFO.
Dear Samuel Mehrbrodt (allotropia), 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 MassPing-UntouchedBug