Description: When one opens a write-protected document, there's no UI indication that it's write protected, when you start to type it throws up a dialog box. It should instead lock the toolbars in an obvious way that the document is locked, there should be no dialogue box never ever, it should not even allow me to place a cursor. Second, the write lock needs to be something I can disable. Disabling the protected content option in the settings just reverts when I reopen settings. Makes zero sense. Terrible UX. It has to remove the lock when I order it to. Steps to Reproduce: 1. Just open a write-protected document 2. Try to change it 3. Some annoying dialogue box jumps in front that has to be manually dismissed Actual Results: Annoying dialogue box, no UI hints that it's locked, no way to disable the lock. Expected Results: No annoying dialogue box, UI hints that the document is locked, an **obvious** way to disable the lock. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.5.2 Build ID: 1:6.4.5-0ubuntu0.20.04.1 CPU threads: 24; OS: Linux 5.6; UI render: GL; VCL: kf5; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
That's not how it worked for me. (Ubuntu 20.04, cinnamon). I can't reproduce. I used the file system to make an ODT file read-only. (chmod 444). When I open the file - the blue bar tells me it is read-only. If I tell it to edit anyway, I am able to edit, and when I try to save, it prompts for a new filename.
Not talking about POSIX-like file permissions.
(In reply to Avamander from comment #2) > Not talking about POSIX-like file permissions. Then attaching an example document would be helpful.
Dear Avamander, 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 Avamander, 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