Description: In a shared folder User A has read access and User B has write access on file system level(NTFS). User A opens an xlsx-file with Calc in Read Mode. User B opens the same file with Excel to modify it. As long as User B has opened the file User A is not able to save it. Steps to Reproduce: 1. User A opens an xlsx-file with Calc in Read Mode. 2. User B opens the same file with Excel to modify it. 3. User B tries to change and save the file but gets an error message saying that an other user has opened the file. Actual Results: A file that is opened in Read Mode is not changeable from an other user. Expected Results: A file that is opened in Read Mode should be changable from an other user, as ist was in Version 6.3 and before. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.4.7.2 (x86) Build-ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU-Threads: 8; BS: Windows 6.3 Build 9600; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
I could not reproduce, using an XLSX file, opening it in read-only on Ubuntu 20.04 with: libreoffice6.4 --view "path/to/file.xlsx" ... and opening and editing the same file on Windows 10 with LO 6.4 or MS Excel. Marco, if you still have a setup that allows it, could you please test again with a version that is currently supported? (7.4 or 7.5) Thank you!
Dear Marco, 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 Marco, 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