1. Open a Writer Document. 2. Write something, so that you have more than one page of text. 3. Search for a text that IS NOT in the document => of course nothing is found. 4. Search again by pressing the "find next" or the down arrow symbol => again nothing is found, but the document is scrolled to the beginning of the document. 5. Search for a text that IS in the document => nothing is found. Only when you search again then the text is found. 1:5.1.5~rc2-0ubuntu1~trusty1 de-DE (de_DE.UTF-8)
Not reproducible on: Win10x64 Version: 5.1.5.2 (x64) Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5 CPU Threads: 1; OS Version: Windows 6.19; UI Render: default; Locale: es-ES (es_ES); Calc: CL
Tested with Ubuntu Live CD (64 bit): 5.1.4.2 also has this bug, so I'm changing the Version number. 4.2.8.2 works ok. It gives the message "Do you want to continue at the beginning? LibreOffice Writer has searched to the end of the document." which is not present in 5.1.4.2 , so there was a redesign/change in the Find dialog.
Reproduced in Windows 7 and Ubuntu 16.04 with a couple of different versions between 5.0.0.5 and 5.2.1.1. Not reproduced with 4.4.0.3. => regression. Migual, can you try with these (maybe slightly more) precise steps: 1. Start a new document. 2. Type "something". 3. Press Ctrl-F, and search for not existing word "fig" by pressing Enter (do this 2x). You'll get result "Search key not found" as expected. 4. Search for "something" by pressing Enter. Bug: you will get result "Search key not found" (second Enter will jump to the word)
Seems it happens sometimes but not always. Versión: 5.0.6.2 (x64) Build ID: b3fbfa99158a1030fb79f0ba72b6851afc3c7895-GL Not reproducible: Version: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
No repro: Version: 5.3.0.0.alpha0+ Build ID: 73c7e0921d752df53004ed55735f3e8888cc592f CPU Threads: 4; OS Version: Windows 6.1; UI Render: default;
Still occurs for me with steps described in comment 3. Version: 5.3.0.0.alpha0+ Build ID: cf4ff92144726a91508fcaf4be21170eac5cb99a CPU Threads: 4; OS Version: Windows 6.1; UI Render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2016-10-01_00:13:03 Locale: hu-HU (hu_HU); Calc: group
This seems to have begun at the below commit. Adding Cc: to Aybuke Ozdemir; Could you possibly take a look at this one? Thanks Steps in comment 5: 1. open to Start Center 2. press and release Alt, then Down, then Right, then Enter. (this will lead to the same menu item as Alt+F, N, T) Fails only on the launch case from the Start Center on initial launch. author Aybuke Ozdemir <aybuke.147@gmail.com> 2015-10-23 20:12:08 (GMT) committer Katarina Behrens <Katarina.Behrens@cib.de> 2015-10-27 15:48:24 (GMT) commit 9b322ace3b8f316104f7138b082d2ffdb282c816 (patch) tree 8b6af4882088744d1a1217cd4108889a0002a66f parent ce15c93cec284440244e63bea75a016e9f2c9f04 (diff) tdf#88548 fontwork gallery always have transparent/checkered background. source 9b322ace3b8f316104f7138b082d2ffdb282c816 $ git bisect log # bad: [05d11632892a322664fb52bac90b2598b7fb7544] source 5616d22b57a9a5e57d545e912e029162a230829b # good: [c1efd324c6ad448ac9edb030dc9738b9e6899e4d] source ab465b90f6c6da5595393a0ba73f33a1e71a2b65 git bisect start 'origin/master' 'oldest' # good: [97526ab777da7e58ce283c05498262ecdd4d6f7f] source 4ea70f87f7a2b61eda6e5ab1f48debf6fcfadc1f git bisect good 97526ab777da7e58ce283c05498262ecdd4d6f7f # good: [86fee7ded76d9c2756ccab6aef160a2d7fab0ab6] source 1b62841b1859ae3443e2bf1ebe99ec3d6afb6cc2 git bisect good 86fee7ded76d9c2756ccab6aef160a2d7fab0ab6 # bad: [11864a7db429a57aeea021e0b3f1fb1412282d32] source e5b721a14c1c8e5261a70588b30353cbb5bd55c6 git bisect bad 11864a7db429a57aeea021e0b3f1fb1412282d32 # bad: [cec39174971f789b01d212afe8b5ffdd1ba466ca] source 76e75d2dd6dafe55fd1740693529640652ed6455 git bisect bad cec39174971f789b01d212afe8b5ffdd1ba466ca # good: [a8a2139bffcee59cfb8887106ac3f9bc6569cf9a] source 1848581f4f3a3f22e2d104a2890699c26d35e1e8 git bisect good a8a2139bffcee59cfb8887106ac3f9bc6569cf9a # bad: [51e0379831d38049a498ff5d6c70eb647c93dee8] source ac630469789b8b1fd93d3ae90acae83ed463d756 git bisect bad 51e0379831d38049a498ff5d6c70eb647c93dee8 # good: [ac87de9d4ee0020419ad1961156de4ac0321ec02] source 7bcd8ed0faaefb8fe3783d6e31dea5c727eddc2a git bisect good ac87de9d4ee0020419ad1961156de4ac0321ec02 # good: [f6420ff1264f1c468f3fbd5bf5429ff1b68b6b88] source 30cdd16cbfaaa34fd0da010bf4de18f9d649d22e git bisect good f6420ff1264f1c468f3fbd5bf5429ff1b68b6b88 # good: [884b901996cd55a4df0bfce490d3e842a291868a] source f99e8f84f5421076b6c0c10a592e43843eabd8ff git bisect good 884b901996cd55a4df0bfce490d3e842a291868a # bad: [1a5c56aa14e7b9a325cbb732a929b93eaebb7f1a] source 125f0c95b7f5613d71bcf107b73a0ba422d54643 git bisect bad 1a5c56aa14e7b9a325cbb732a929b93eaebb7f1a # good: [77442162720ce0a97195319f3782dce9bdf9d33c] source 623f5b26ffd77041d0b06d7ce9c3b32d05625440 git bisect good 77442162720ce0a97195319f3782dce9bdf9d33c # bad: [b52018ea405c53d0c3cf4cd465ffd1dc80dd15a1] source 9b322ace3b8f316104f7138b082d2ffdb282c816 git bisect bad b52018ea405c53d0c3cf4cd465ffd1dc80dd15a1 # good: [ad463231323943d069dae745ebc4b8eea2ced3ad] source ce15c93cec284440244e63bea75a016e9f2c9f04 git bisect good ad463231323943d069dae745ebc4b8eea2ced3ad # first bad commit: [b52018ea405c53d0c3cf4cd465ffd1dc80dd15a1] source 9b322ace3b8f316104f7138b082d2ffdb282c816
(In reply to raal from comment #7) > This seems to have begun at the below commit. > Adding Cc: to Aybuke Ozdemir; Could you possibly take a look at this one? > Thanks > Sorry , wrong bug
(In reply to el from comment #0) > 4. Search again by pressing the "find next" or the down arrow symbol => > again nothing is found, but the document is scrolled to the beginning of the > document. This part itself is already annoying: It troubles the user to manually go back to the original place in the document (which may be far away in a long document). [Note: I've been depending on a workaround by using Undo and Redo, if possible.]
The Summary "Searching for text doesn't find it the first time after searching for text that is not in the document" is a bit confusing to me, but I understand the difficulty of wording the bug. OP, are you ok with this? Problem occurs after searching for text NOT found in document We then let others find out the details of the problem in your Description.
*** Bug 104690 has been marked as a duplicate of this bug. ***
(In reply to Kumāra from comment #10) > The Summary "Searching for text doesn't find it the first time after > searching for text that is not in the document" is a bit confusing to me, > but I understand the difficulty of wording the bug. > > OP, are you ok with this? > Problem occurs after searching for text NOT found in document > > We then let others find out the details of the problem in your Description. Sure, you can change the description if that makes it better understandable.
Not in range of Linux bibisect-50max repo.
Bibisect log with bibisect-win32-5.1 repo: d935f80258c4fcd6ec506a8f3cc20df1a3808945 is the first bad commit commit d935f80258c4fcd6ec506a8f3cc20df1a3808945 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Mon Jul 13 16:14:38 2015 -0700 source 8d2fe8d7e5f374f3a106a4fc58ef597a52815ad0 # bad: [9e5a3578641c56a4d31caf444afe7da3be3e23e8] source 2a5a4497c210b649fdfaae8b74d742f23df32499 # good: [c1efd324c6ad448ac9edb030dc9738b9e6899e4d] source ab465b90f6c6da5595393a0ba73f33a1e71a2b65 git bisect start '9e5a357' 'c1efd32' # bad: [b1869e4d731b240df0f8cdff25f003a5b6e941f5] source ad62165065a0f96933d8b491770775bb57ac51bd git bisect bad b1869e4d731b240df0f8cdff25f003a5b6e941f5 # good: [5db1f74c5b779b66578984a443fd48a31d33c44e] source 60391b4726b6c00950fddb6088ffcc0a1ae142bc git bisect good 5db1f74c5b779b66578984a443fd48a31d33c44e # bad: [46eb0921378c939469eac9b457bcf04ce73f78c5] source 0deb0326b32cdb2b90b620b3403128196c2d4d74 git bisect bad 46eb0921378c939469eac9b457bcf04ce73f78c5 # good: [0e16aaea772647b186b3f17e22da490f849f5b4b] source f749a970e2927ed703a5b7c70e393b5ba6c35e22 git bisect good 0e16aaea772647b186b3f17e22da490f849f5b4b # bad: [2aaed3bb6d897b3b392f082259ebe263f775a9d1] source cd5d3c4054868c02fce12016edcf9584013b48bf git bisect bad 2aaed3bb6d897b3b392f082259ebe263f775a9d1 # good: [d9e6a56010fdc16da87f971c2963898259f0ca89] source b4f9145fb4cfa8cee6fb52c647adb45712453eca git bisect good d9e6a56010fdc16da87f971c2963898259f0ca89 # good: [61ada77ea26a9dee45c0a69e3f67f565e73f2ebf] source bf93b3d1a4b624c3b58e6429899c47fa7cad6ede git bisect good 61ada77ea26a9dee45c0a69e3f67f565e73f2ebf # bad: [ca3b5c00e2b1f98161bcd43e253311cbf42f49dc] source a69d89435d12529c1af818bc72192588d8abea18 git bisect bad ca3b5c00e2b1f98161bcd43e253311cbf42f49dc # bad: [d0ab15a437e47b5b32e895aaaeceafe3b82cfd62] source d60719015e1a82873b39565b77c24e6ae28edd24 git bisect bad d0ab15a437e47b5b32e895aaaeceafe3b82cfd62 # bad: [d935f80258c4fcd6ec506a8f3cc20df1a3808945] source 8d2fe8d7e5f374f3a106a4fc58ef597a52815ad0 git bisect bad d935f80258c4fcd6ec506a8f3cc20df1a3808945 # good: [f9128307882cf4bc732b613e4b7370e0e5fd07d1] source 83f25d3c6e0918a1d29aa3a923b7f35f0b8a55e2 git bisect good f9128307882cf4bc732b613e4b7370e0e5fd07d1 # first bad commit: [d935f80258c4fcd6ec506a8f3cc20df1a3808945] source 8d2fe8d7e5f374f3a106a4fc58ef597a52815ad0
Bug started with the commit listed below. Adding Cc: to Miklos Vajna, please take a look. https://cgit.freedesktop.org/libreoffice/core/commit/?id=8d2fe8d7e5f374f3a106a4fc58ef597a52815ad0 author Miklos Vajna <vmiklos@collabora.co.uk> 2015-06-03 07:03:48 (GMT) committer Miklos Vajna <vmiklos@collabora.co.uk> 2015-06-03 07:20:14 (GMT) "SwView::SearchAndWrap: fix WrapAround search in fly frames"
*** Bug 114454 has been marked as a duplicate of this bug. ***
** 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 repro. Version: 6.3.0.0.alpha0+ Build-ID: be8897d9c63a77b223a9c0aed1d2eb689e0e0082 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-02_04:49:04
(In reply to Aron Budea from comment #3) > 1. Start a new document. > 2. Type "something". > 3. Press Ctrl-F, and search for not existing word "fig" by pressing Enter > (do this 2x). You'll get result "Search key not found" as expected. > 4. Search for "something" by pressing Enter. I'll look at this.
Miklos Vajna committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/9c1383e4da135db28c422752153e9a77558e8c2f%5E%21 tdf#101873 sw: fix search for second term after double not found It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Miklos Vajna committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/62c1acdda27966c810cab25a1d0667c6a18c436d%5E%21 tdf#101873 sw: fix search for second term after double not found It will be available in 6.2.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Zdeněk Crhonek committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/92849660e21d5a13fb671339e52cbc30335ab842%5E%21 uitest for bug tdf#101873 It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Miklos Vajna committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/971788dd2caa218321714f5e79a29349f934a01c%5E%21 Revert "uitest for bug tdf#101873" It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Issue verified in Version: 6.3.0.0.alpha0+ Build ID: 8aa579830b20072af8d6e149d6b279362fe98b91 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded @Miklos, thanks for fixing this!