A user has created a file in MS Excel and set it to protected mode which defaults the user to open the file in Read Only mode. When opening the file in MS Excel, this correctly opens in Read Only mode and only when you try to "Enable Editing" does the file switch to Read-Write mode. When opening (by double clicking on the file) the same file in LibreOffice it correctly opens in Read Only mode (as shown on the task bar) but it still creates a -lock file. When a second user opens the file in MS Excel or LibreOffice the file says it is locked and can only be opened in Read Only mode. Now with the document closed in both Excel and LibreOffice .... Open LibreOffice and from the File Menu, open the document but tick the "Read Only" checkbox and proceed to open the document. Now the document pens but NO .~lock file is created. Now when opening a second instance of the document from either LibreOffice or Excel the application correctly assumes the document is not locked by a user and thus opens the document. The bug here seems to be when you open the document by double clicking on the file and opening in LibreOffice instead of Opening the document in RO mode from the File/Open menu. I have tested this in LibreOffice 6.4.5 and 7.0.0+ Thank you
> > The bug here seems to be when you open the document by double clicking on > the file and opening in LibreOffice instead of Opening the document in RO > mode from the File/Open menu. > From my perspective the issue is that LibreOffice doesn't honor the "Open Read-Only" setting from the document at all when it comes to create a lock file or not. A lock file is always created, regardless of the documents settings. Only selecting "Read-Only" in the file picker dialogs prevents from lock file creation.
> From my perspective the issue is that LibreOffice doesn't honor the "Open > Read-Only" setting from the document at all when it comes to create a lock > file or not. A lock file is always created, regardless of the documents > settings. Only selecting "Read-Only" in the file picker dialogs prevents > from lock file creation. ... and I'd state the bug the following: LibreOffice doesn't remove the lock file after having opened a file and recognized that it has a read-only setting.
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
Attaching an example file in protected mode would be nice... I tried to create a protected spreadsheet in Excel 2003, and failed.
Created attachment 171410 [details] Empty Spreadsheet, created as "new empty file", but then saved as xlsx and marked as "open in write protect mode"
This is an (otherwise empty) spreadsheet. When opened in Calc by double clicking, there are created: .~lock.OpenDocument Tabellendokument (neu).xlsx# ~$OpenDocument Tabellendokument (neu).xlsx Calc is nevertheless in write protected mode. Calc 7.0.4.2 (x64), Win 10
Sorry, don't know which files are created (and immediatley deleted, maybe?). I meant "there are existing"
example file added
(In reply to Peter from comment #5) > Created attachment 171410 [details] > Empty Spreadsheet, created as "new empty file", but then saved as xlsx and > marked as "open in write protect mode" Of course the other way around. 1st created (by means of explorer's "new file" menu, opened with Calc 7.0.4.2, there marked as ..., then saved as xlsx
Hello, It's been a while since this issue was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Mark Sammon, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Mark Sammon, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp