Created attachment 47348 [details] Simple test document When opening a .doc file which has security set to read-only, the file opens read only in Writer (as expected). *However*, when choosing to manually enable editing (by clicking the "Edit File" icon), the content comes appears in an protected section. A test document is attached. Upon opening, it is set to read-only. Clicking "Edit File" changes the *document* property to editable, but the content is shown to be in a protected section. A work-around is to enable document editing, and then to manually unset the protection on each section in the document. (Format->Section, untick "Protect") Opening this file in Word 2010 brings up a dialogue stating: <File> should be opened as read-only unless changes to it need to be saved. Open as read-only? [Yes] [No] [Cancel] [Help] If, in Word 2010, one says "no" to that prompt, the file is completely editable (*no* protected sections). At least one person in the office here has been incredibly frustrated by not being able to edit a document no matter what he tried. I suspect this is an import error, as well as a UI problem. (We need to be clearer about opening read-only files). Tested under Linux/LibO3.4RC2 and Windows/LibO3.3
RC2 is bit by bit identical with release version, so separate items in the version picker are useless. Changes have been discussed with Michael Meeks.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced in LibO 3.6.0 master on Fedora 64 bit document has one section when opened, but probably so should be
Reproduced also in 3.5.0RC2 running on Fedora 16, x86_64
reproducible with LO 4.0.2.2 (Win7 Home, 64bit)
Still persists in 4.1.2.3.
Still present in 4.2.5.2 (Fedora 20, x86_64)
Reproduced in LO 4.3.0.2, 3.3.0.4 (Ubuntu 12.04 x86). Also with AOO 4.1.0 So best guess is an old issue inherited from OOO
Persisting OS X 10.10.3 Version: 5.1.0.0.alpha1+ Build ID: fb6dd2a73074b9695bd8ddf7ba40f1819b03024e TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2015-06-17_23:34:12 Locale: de-DE (de.UTF-8)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still reproducible in Version: 6.0.0.0.alpha0+ Build ID: 34e8fd7e99489e9f50a512b07c6f3923b358b4d3 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present Tested in latest nightly build: Version: 6.2.0.0.alpha0+ Build ID: e7d5bad5ae083da12c3ec4a4a8bdc8b42447a242 CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: kde4; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-10-06_01:01:43 Locale: en-AU (en_AU.UTF-8); Calc: threaded
Proposed fix at https://gerrit.libreoffice.org/61899
Justin Luth committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=8ba20167034f38ea2984bc8fb0e785da107cb82b tdf#37778 ww8import: protect section only if protEnabled It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.