In the previous versions, at the Find and Replace window, if I click to the Replace button, Writer replaced the text and jumped to the next search result. At now, the jumping is missing, so if I want to change a lot of occurrence, I must alternate between buttons Find and Replace. Operating System: All Version: 4.0.6.2 release
Hi Zoltán, thanks for the issue. I see that it works fine for me both in 4.0.6.2 and 4.1.3.2 on Ubunutu.. In writer anyway. Can you pls check again? regards, Cor
(In reply to comment #1) I checked a lot of times, 4.0.6.2 release. This error maybe not happen in Linux. I am using Windows Xp Home SP3, so I modified the hardware from all to Windows.
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
I can trigger this bug for localc (4.2.4; wheezy-backports 1:4.2.4-3~bpo70+1): 1) Open a new spreadsheet. 2) Type 1 in A1 and again in A2 3) Select A1 4) Find&Replace: replace 1 by 21. Each time Replace is clicked a 2 is added before the 1 (i.e., 1->21->221->2221 etc.). The search does not advance without an explicit click on Find in between. Note: Excel2013 advances before the next replace as expected (in case there is a need for a precedent). Gnumeric does not advance (with only A1 select) without an explicit Find in between but it doesn't pretend to; you have to explicitly select the ranges you wish to change.
(In reply to comment #4) > I can trigger this bug for localc (4.2.4; wheezy-backports > 1:4.2.4-3~bpo70+1): > > 1) Open a new spreadsheet. > > 2) Type 1 in A1 and again in A2 > > 3) Select A1 > > 4) Find&Replace: replace 1 by 21. Each time Replace is clicked a 2 is added > before the 1 (i.e., 1->21->221->2221 etc.). The search does not advance > without an explicit click on Find in between. > TESTING Linux Mint 17 4.3.0.4 Reproduced by following the steps above. The "1" in A1 is replaced over and over again because "21" has a 1. IF the replace search replaces the "1" by "12", it behaves the same way, the "12" has a 1. IF the replace search replaces the "1" by "22", it behaves normally: It replaces the 1 in A1 and then jumps to A2, and then it no longer has anything else to replace. I also tried it with 2 in A1 and the 2 in A2 Then the find and replace search for 2 to replace with 21. And the bug is reproduced again. Conclusion: Any number that is replaced by another number that includes the first number will create this bug 1 -> 12 1 -> 21 1 -> 17 2 -> 21 3 -> 36 etc
I can confirm problem in comment 4 since LO 3.3.0.4, and also with AOO 4.1.0. But this bug originally reported against Writer, how could this turns into Calc? @Zoltán, do you still have that problem within Writer in latest stable release?
[ > @Zoltán, do you still have that problem within Writer in latest stable > release? I guess not ;) ] Apart from that: the behavior in Calc is like this from OOo times. Luckily there are shot cuts on Next / Replace buttons.
** 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
Dear Zoltán Hegedüs, 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
it works as expected in: Version: 7.1.0.3 / LibreOffice Community Build ID: 10(Build:3) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear Zoltán Hegedüs, 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