Created attachment 123310 [details] Sample files to reproduce the problm I pasted text and the associated comment from old-doc to new-doc, then began adding to (editing) the comment. Then I wished to check that I had not (previously) changed the text in new-doc that the comment was attached to. So I used Undo until the changes I'd just made were all gone; found that I had /not/ made any changes to the text, and then tried to Redo all the edits. All changes except the two edits I'd made to the copied-comment "re-played". (The changes were: deleting a leading blank line at the start of the comment, and then appending a newline and the text "[L]]" at the end of the comment. While a minor problem, it seems indicative of a possibly-serious logic error, and thus worth reporting. I was able to reproduce it with the attached two tiny files. Steps to reproduce: 1. Open both docs. 2. In "old", copy the text "black as pitch" and its associated comment. 3. Select the text "black as pitch" in the "new" doc, and paste to replace the text and add the comment. 4. Click into the comment in "new" and delete the empty blank line. click to the end of the comment and Type <enter><enter>[L]<enter> 5. Undo all change to "new". 6. Redo until no further changes occur. Result: The edits made to the comment itself in "new" are not "replayed".
It said: The file 'Incomplete-Redo-new-doc.odt' is corrupt and therefore cannot be opened. It works for you? 64-bit, KDE Plasma 5 Build ID: 5.1.1.3 Arch Linux build-2 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 4bf2b6b2e6641c82e2b714e394482f1a1620b436 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on March 21st 2016
Interesting. I created the document in LO 5.1.0.3: the fact that the new doc is corrupt when seen by LO5.1.1.2 is interesting. Yes, I experience the same behaviour you describe. But if I allow LO to repair the document and proceed by following the steps I described in the original report, the same redo problem occurs. I also checked that if I save the repaired Incomplete-Redo-new-doc.odt, close both docs and then follow the steps for the repaired doc and the old doc, the problem again is perfectly reproduced. I don't still 5.1.0.3 installed, so I can't easily check to see what it thinks of Incomplete-Redo-new-doc.odt. It seems very strange to me that a tiny document created by LO is seen as corrupt! Do you think the nature of the corruption might be worth investigating, too? (Especially since the file is only 21 words long.)
Ok, going through the steps, when I redo, there does not appear a blank line before the comment text. First a blank comment appears and then the text appears without the blank line. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 011e65c93053c88eb752e50ef47c69872608cbcd CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on March 22nd 2016
So if I understand you correctly, you're confirming that the deletion of the blank line in the comment is not undone, nor is the new text (in this case, \n[L]\n\n) redone.
I was focusing on this: "Result: The edits made to the comment itself in "new" are not "replayed"."
Undo/Redo in comments seems to work until the comment itself is removed This works: - change text in a comment - undo to the beginning of the change and redo -> works This fails: -insert a comment, insert text into the comment -undo all and redo -> you get an empty comment This fails - a bit simpler as in the initial description -copy some text with an attached comment and paste it -change something in the comment -undo and redo -> the comment appears as pasted, subsequent changes are gone
** 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.2.7 or 5.3.3 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-20170522
Dear Luke Kendall, 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
Dear Luke Kendall, 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
Thanks, bug is now fixed. Version: 7.2.3.2 / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded