Hi All, Stumbled across this while doing some examples for bug 106723. This seems to only happen when the search string is found at the beginning or end of a document and no other places in the document. Steps to repro incorrect search result at end of a document: 1) Open a new document in Writer and enter "This is a sentence to test search not found bug" 2) Open the find toolbar Menu > View > Toolbars > Find or Ctrl+F 3) In the find text box enter "bug" without quotes 4) Click on the "Find Next" button "Reached the end of the document" is displayed in the find bar message area and "bug" is selected in the document. 5) Click on the "Find Previous" button Results: "Search key not found" is display in the find bar messages area. Expected results: "Reached the begining of the document" should be displayed in the find bar message area as can be seen by clicking on "Find Previous" button after the incorrect "Search key not found" message is displayed. Steps to repro incorrect search result at beginning of a document: 1) In the find text box enter "This" without quotes 2) Click on the "Find Previous" button 3) Click on the "Find Next" button Results: "Search key not found" is display in the find bar messages area. Expected results: "Reached the end of the document" should be displayed in the find bar message area as can be seen by clicking on "Find Next" button after the incorrect "Search key not found" message is displayed. I repro back to version 5.2.8.0.0+
I can confirm with Version: 6.3.0.0.alpha0+ Build ID: 82463bdde75447d45e0cd6ed9ab579e0e51ea912 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; It works as expected if word "bug" is not last word, even it works if spaces are after word "bug".
Dear Jim Raykowski, 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://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 repro in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 78c33a4c3d1633b97049874305b3b49b820395a2 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded
Dear Jim Raykowski, 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
Still exists in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ced4a9221329b88484f90ab6d00d797f024585bb CPU threads: 2; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded