Red Hat Bugzilla – Bug 469379
Evince 'Find' can get stuck on a page
Last modified: 2010-10-23 01:30:36 EDT
Created attachment 322091 [details]
patch to fix find problem
Description of problem:
Evince's search function gets stuck on one particular page unless you scroll the buffer.
Steps to Reproduce:
Open up a document such as: http://download.intel.com/design/chipsets/datashts/318610.pdf
Search for something like NERR_FAT_FB and repeatedly hit the find next button. When you get to the instance on page 220 184.108.40.206 it will get stuck until you scroll the page down a bit.
it gets stuck
it moves to the next instance even if it isn't on the same page
It seems to happen when there are multiple instances of the search string on the same page. It seems to work properly when there is only one instance on the page.
2006-10-08 Nickolay V. Shmyrev <firstname.lastname@example.org>
* shell/ev-view.c: (view_set_adjustment_values),
Fixes bug #343199, current page now follows find page.
might fix it.
Seems to work for me.
Attached a patch
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
setting for 5.5
I committed the backported patch from upstream.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
When searching for a string in a document, evince may have miscalculated the scope of the search if a string appeared more than once on a single page. Consequently, if a user was stepping though the search results using the "Find Next" button, evince would not step past the page with multiple matches. With this update, evince now correctly searches the whole document, resolving this issue. (BZ#469379)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.