Opening a file on a cifs mount on Linux from libreoffice-6.3.5.2, some MS Office Professional Plus 2019 fails to open with "... is currently used by another person. Please try again later." 1. The locking user is not reported on MSO, eventhough both locking files for LO and MSO are created and owned by my user. 2. There is no way to open a read-only copy from MSO. It can't open the file at all.
(In reply to Massimo B. from comment #0) > Opening a file on a cifs mount on Linux from libreoffice-6.3.5.2, some MS > Office Professional Plus 2019 fails to open with "... is currently used by > another person. Please try again later." > > > 1. The locking user is not reported on MSO, eventhough both locking files > for LO and MSO are created and owned by my user. Is the file still open in LibreOffice while you try that? Can you try if changing the "UseDocumentSystemFileLocking" option changes the behavior? Does this work on another file system or is this specific to CIFS? > > 2. There is no way to open a read-only copy from MSO. It can't open the file > at all. This is not our bug, please report this issue to Microsoft.
(In reply to Samuel Mehrbrodt (CIB) from comment #1) > Is the file still open in LibreOffice while you try that? Of course. After closing the file, it is accessible again from MSO. > Can you try if changing the "UseDocumentSystemFileLocking" option changes > the behavior? How and where to do that? I have enabled Options->Load/Save->Microsoft Office->[x] Create MSO lock file. > Does this work on another file system or is this specific to CIFS? I don't have any other shared filesystem with MSO. > > 2. There is no way to open a read-only copy from MSO. It can't open the file > > at all. > This is not our bug, please report this issue to Microsoft. Because in an MSO environment this is all working, I don't think they appreciate a bug report with 3rd party tools.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Massimo B. from comment #2) > How and where to do that? > I have enabled Options->Load/Save->Microsoft Office->[x] Create MSO lock > file. Tools->Options->Advanced->Open Expert configuration. Then search for "UseDocumentSystemFileLocking" and change to false. > > > Does this work on another file system or is this specific to CIFS? > > I don't have any other shared filesystem with MSO. I mean on a local file system like NTFS. Just try on a Windows machine with both LO and MSO installed on the local file system. > > > > 2. There is no way to open a read-only copy from MSO. It can't open the file > > > at all. > > > This is not our bug, please report this issue to Microsoft. > > Because in an MSO environment this is all working, I don't think they > appreciate a bug report with 3rd party tools. Ok.
(In reply to Samuel Mehrbrodt (CIB) from comment #4) > Tools->Options->Advanced->Open Expert configuration. > Then search for "UseDocumentSystemFileLocking" and change to false. This makes a difference. Now MSO can open the file as usual and does not get any information about other people having opened that file. This would not prevent others from changing the file in the background but is currently better here for not blocking other team members. Is it advised to keep this disabled or does it just point to a bug in Libreoffice?
(In reply to Massimo B. from comment #5) > (In reply to Samuel Mehrbrodt (CIB) from comment #4) > > > Tools->Options->Advanced->Open Expert configuration. > > Then search for "UseDocumentSystemFileLocking" and change to false. > > This makes a difference. Now MSO can open the file as usual and does not get > any information about other people having opened that file. > This would not prevent others from changing the file in the background but > is currently better here for not blocking other team members. > Is it advised to keep this disabled or does it just point to a bug in > Libreoffice? The bug might as well be in the CIFS implementation. Not easy to say. I guess it's safe to disable this setting, as the overwriting is prohibited by the lockfile. Maybe it even makes sense to disable this setting by default? Looks like it does not work reliably on network shares. See also bug 131388.
Documentation for the bug and all payment is fit for the host of the trials for the field. The like of the team and https://my-assignment.help/nursing-assignment-help/ is surd for the changes. The nature is rough for the approval of the mixing of the goals for the team for functions.
Dear Massimo B., 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
I can confirm this bug with Libreoffice 7.4.6.2. If UseDocumentSystemFileLocking is false and other locking options are default, then MS Office (tested with Word 365) can open and save documents, which are already opened in Libreoffice (LO). There is no notification both in LO and MS Office, that someone already has opened the file. LO creates a .~lock.originalfilename# lock file, which is ignored by MS Office. If UseDocumentSystemFileLocking is false and CreateMSOLockFiles is true there is also no notification in MS Office, if the file is already opened in LO. There is a MS Office compatible lock file ~$partoforiginalfilename, but MS Office ignores it. If UseDocumentSystemFileLocking is true (default), MS Office can not open the document, which is already opened in LO. Copying the file is also impossible in Windows then.