Launchpad has imported 22 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=36582.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-04-25T06:41:49+00:00 Magnes wrote: If you turn on recording and showing changes in document find and replace will replace even things already deleted. Example: 1. Create new document. 2. Write "This is a document". 3. Turn on showing and recording changes. 4. Delete the word "document" so you have "This is a". 5. Replace document with "file". 6. The document will contain: "This is a file." instead of "This is a". Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/0 ------------------------------------------------------------------------ On 2011-04-25T06:43:03+00:00 Magnes wrote: PS. In point 5 I mean "Use search and replace to change word 'document' to 'file'". Sorry for being vague. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/1 ------------------------------------------------------------------------ On 2011-04-25T11:19:23+00:00 Gleppert-o wrote: I tested the bug as described. I can confirm the bug on my system. Furthermore, the bug is even more serious than described: * First problem as described by Tomasz: The replace deleted word is active/undeleted after search&replace. This actually destroys the written text. * Second problem: After hitting "Replace all" a couple of times, it will keep replacing the deleted text with the new text. The dialog never displays "Word not found" and hence does not stop. Due to the reason that data can be actually made unusable/unreadible, I change the importance to high/major. I hope this is okay. System: Ubuntu 10.4./Gnome, LibreOffice 3.3.2 PPA, Intel 32Bit Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/2 ------------------------------------------------------------------------ On 2011-12-23T12:07:33+00:00 Björn Michaelsen wrote: [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 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/3 ------------------------------------------------------------------------ On 2012-02-11T19:30:57+00:00 Chuck598 wrote: No longer does find & replace work for me. I have deleted LibeOffice & reinstalled & no change. Maybe there is a report that I didn't see about this or maybe only me? I am only a user so not to good & this as this is the first time I have tried to report a problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/4 ------------------------------------------------------------------------ On 2012-03-19T09:45:16+00:00 Gleppert-o wrote: This severe regression is still there in LibreOffice 3.5. I just 'destroyed' a document myself where track changes was activated (and extensively used) and I wanted to search&replace something. Please increase the severity of this bug! Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/5 ------------------------------------------------------------------------ On 2012-10-15T19:55:15+00:00 Stfhell wrote: Still a problem in LO 3.6.2.2. In summary: When "Show tracked changes" is active, "Find" will find text that has been deleted with "track changes" activated. "Find & replace" will replace already deleted text. When you do "Find & replace" with activated "track changes", it will replace the same (already deleted) text again and again. "Replace all" works insofar as it replaces each occurance only once. Actually it can be useful if "Find" also searches tracked deletions - after all you use "track changes" to be able to keep deleted text in the document. But I think it's usually not what you want. So you would have to disable "show tracked changes" just to do a "Find". I cannot imagine a situation where you would like already deleted text to be replaced by newly inserted text. It's definitely a bug that LO does not at least move the cursor behind the replaced text when you choose "Replace" in the "Find & replace" dialogue with "track changes" activated. That leads to the same text being replaced again and again. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/6 ------------------------------------------------------------------------ On 2012-12-18T17:22:53+00:00 Michael-stahl wrote: please somebody tell me which OOo/LO version did not have this bug. i can reproduce it going back to OOo 3.0.1, so doesn't look like a regression. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/7 ------------------------------------------------------------------------ On 2012-12-18T20:08:47+00:00 Stfhell wrote: I can't remember that this has ever worked differently. The corresponding OOo bug was filed in 2007 for OOo 2.3: https://issues.apache.org/ooo/show_bug.cgi?id=82591 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/8 ------------------------------------------------------------------------ On 2014-02-28T12:45:56+00:00 Björn Michaelsen wrote: Bulk change: Bibisected bugs can be assumed to be regressions. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/22 ------------------------------------------------------------------------ On 2014-02-28T12:49:27+00:00 Michael-stahl wrote: removing erroneously added "regression", see comment #7 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/23 ------------------------------------------------------------------------ On 2014-07-30T09:46:46+00:00 Xiscofauli wrote: According to comment 7 this isn't a regression, thus remove bibisected35 bibisected35older from whiteboard Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/24 ------------------------------------------------------------------------ On 2015-09-04T02:49:51+00:00 Qa-admin-q wrote: ** 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.0.0.5 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/26 ------------------------------------------------------------------------ On 2015-09-04T09:22:21+00:00 Xiscofauli wrote: This issue is still present in Version: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: es-ES (es_ES) on Windows 7 (64-bit) Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/27 ------------------------------------------------------------------------ On 2016-09-20T10:32:28+00:00 Qa-admin-q wrote: ** 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/29 ------------------------------------------------------------------------ On 2016-09-22T20:24:53+00:00 Gerry-treppel wrote: Bug still present in Version: 5.1.4.2 Build-ID: 1:5.1.4-0ubuntu1 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/30 ------------------------------------------------------------------------ On 2017-04-20T15:51:27+00:00 timur wrote: *** Bug 65056 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/31 ------------------------------------------------------------------------ On 2018-04-21T02:33:50+00:00 Qa-admin-q wrote: ** 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/32 ------------------------------------------------------------------------ On 2018-04-21T07:30:31+00:00 Gerry-treppel wrote: This bug still exists in LO 6.0 and is still very annoying. Example: If you work with long documents in a team, track changes is often enabled. If you then, for example, replace the British "ise" / "isation" with "ize" / "ization", then you end up with lots of rubbish in the document. LibreOffice Writer does also replace the string in all deleted words and displays the replaced string as not deleted (!). In other words, everywhere in the document are nonsense "ize" / "ization" strings, which you have to manually clean. -> extremely annoying and time-consuming bug! Version: 6.0.3.2 Build-ID: 1:6.0.3~rc2-0ubuntu0.16.04.1~lo2 CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk2; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/33 ------------------------------------------------------------------------ On 2018-04-21T08:07:07+00:00 Gerry-treppel wrote: IMHO there are two possible ways to fix this bug: Either: (1) Writer should not find search strings in deleted text at all (meaning text deleted in Track Changes mode) Or: (2) Writer still finds search strings in all text (including deleted text in Track Changes mode) and also replaces them, but replaced text should be flagged as deleted. Solution 1 is preferable to solution 2. However, if solution 2 is easier to implement, IMHO it would be also okay. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/34 ------------------------------------------------------------------------ On 2019-04-22T02:56:36+00:00 Qa-admin-q wrote: ** 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/35 ------------------------------------------------------------------------ On 2019-04-22T07:33:27+00:00 Gerry-treppel wrote: The bug is still present in v 6.1.5.2. I don't have the most recent LO release at hand, so please can somebody test this against the newest version? Generally, I hope that this bug receives some attention. In every larger project (with track changes), I encountered issues related to this bug that I had to clean manually. Is a fix so complicated? Version: 6.1.5.2 Build ID: 1:6.1.5-0ubuntu0.18.10.1 CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3; Locale: en-GB (de_DE.UTF-8); Calc: group threaded Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1126858/comments/36 ** Changed in: df-libreoffice Status: Unknown => Confirmed ** Changed in: df-libreoffice Importance: Unknown => Medium ** Bug watch added: bz.apache.org/ooo/ #82591 http://yourrxstore.com/product-category/buy-tramadol-online/show_bug.cgi?id=82591 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126858 Title: [upstream] Search and replace, with tracked changes on, changing only format of text, causes Writer to hang To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1126858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
