search, next doesn't change pages when needed

[G.M.]

Hi,

I'm using evince/Document Viewer 3.10.0 in latest update of Ubuntu Saucy.

When I do a search, it finds entries and show them in a panel on the left of the document.

However, when I press F3 to go to the next result entry, it has a very strange, wrong and incoherent behaviour:
- In the left panel, the selection correctly circles through the list of possible results,
- In the document itself, the cursor gets stuck in the current page and cirularly alternates but only in the entries found in the current page. Contrarily to the left panel, it does not go to the following entries in the next pages.

This behaviour is strange and incoherent because left panel and document selections do not refer to the same search result entries. It is wrong because it does not allow to navigate between all the results in the document.

[Sebastien Bacher (seb128)]

Thank you for your bug report, I can't confirm that though, it goes to the next pages here. Could you add a small pdf example to the bug?

[G.M. (sexxxenator)]

Hi Sebastien,

This version of Evince shows this behavior with all the pdfs I've tested it with. I'll try to send one small example as soon as possible.

However, I can add something that might help find the problem: I'm using Awesome as a WM and I already noticed some strange behaviors between previous Evince versions and this WM. For instance, when I open a pdf, then move to another "tag", then come back, I can't move inside the pdf pages with the arrows, I need to clic inside the Evince window, then switch to another tag and come back for the arrows to work again. It's as if Evince would not have recovered the mouse focus. However, the other keys, even Home and End do not show this problem...

So something might be wrong between Evince and Awesome with the management of keys and/or focus...

[G.M. (sexxxenator)]

Hi again,

I've found one PDF that shows the problem:
http://ercim-news.ercim.eu/images/stories/EN93/EN93-web.pdf

In fact, doing more tests with this PDF I discovered that the problem occurs only when using the F3 key to go to the next entry. If using the "next entry" arrow on top left of the window, it works.

Cheers

GM

[Sebastien Bacher (seb128)]

Thanks, indeed it behaves uncorrectly sometimes... the issue seems to be 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.

[G.M. (sexxxenator)]

Thanks Sebastien for the link, I've submitted the bug.
https://bugzilla.gnome.org/show_bug.cgi?id=722702

[Sebastien Bacher (seb128)]

Thanks

[hife (hife)]

I have noticed a similar behaviour when dealing with .djvu files, where it seems to occur whenever the current result is located at the bottom of the screen. In this case said result will not be highlighted as darker than other results like it should. The list of results on the left is always empty on .djvu files as well.

[Brian Campbell (bacam)]

As mentioned in the upstream bug report, this was fixed in later versions, probably by

https://git.gnome.org/browse/evince/commit/?id=8d3ac1d8de83f3c6d9c51e9ad2c56e000d4bb4e7

I've made a quick attempt at backporting this to trusty, and it does seem to work now. I'll attach the patch.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "evince-3.10.3-quick-backport.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Brian Norris (computersforpeace)]

This issue is still present on trusty (14.04). I've built the patch from post #8 (with some slight tweaking to the debian packaging info, to get dpkg-buildpackage to complete successfully), and it looks to work OK. Thanks (other) Brian!

Any chance we can get this merged?

[Sebastien Bacher (seb128)]

is that fixed in vivid? if so we could look at backporting the bugfix

[Brian Norris (computersforpeace)]

It's fixed in Evince 3.11 and newer. Evince works fine in Utopic, but I haven't tested Vivid.

The upstream commit and patch are already mentioned and attached (respectively) here, with test results. What more needs to be done? Can the patch be applied?

[Brian Norris (computersforpeace)]

No backport for Trusty?

[Sebastien Bacher (seb128)]

We could backport to trusty, if somebody is interested to help on that please check https://wiki.ubuntu.com/StableReleaseUpdates

Brian, your patch is a good start but the change should be reviewed in detail (your description gives a warning about that) and the bug should be updated with SRU informations (impact, testcase, regression potential)