← Back to team overview

desktop-packages team mailing list archive

[Bug 1364940] Re: highlighted find entry does not correspond to current page


Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: evince (Ubuntu)
   Importance: Undecided => Low

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.

  highlighted find entry does not correspond to current page

Status in “evince” package in Ubuntu:

Bug description:
  1. open a PDF

  2. open the find functionality (<ctrl>-f).

  3. type a common word like "the".

  4. click on one of the matches on the left.

  5. move to another page with "the" on it.

  6. click the "find next" button (or <ctrl-g>).

     one of the "the"s on the current page is highlighted.

     the next the on the original page is highlighted.

  The problem is that I often use the find so that all the occurences of a word are highlighted.  I find a particular occurrence and then scroll while looking at the context.   There is no quick and easy way to know which match I am currently looking at.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  3 15:14:19 2014
  InstallationDate: Installed on 2013-10-03 (334 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (133 days ago)

To manage notifications about this bug go to: