Bug 191343 - Okular "Next Page" and "Previous page" buttons function erratically - pages not redrawn
Summary: Okular "Next Page" and "Previous page" buttons function erratically - pages n...
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.8.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-02 15:03 UTC by Philip Stephenson
Modified: 2011-12-27 22:18 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Stephenson 2009-05-02 15:03:21 UTC
Version:           0.8.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-11-generic

When viewing any pdf document in okular, the Next-Page or Previous-Page buttons do not work; that is, when clicked once, the new page does not show unless, say, the page is resized, at which point the new page appears.  So, the problem seems to be that the page view is not refreshed when the page is changed.

Note that clicking either of the next/previous page buttons twice will advance/regress the page view a single page, but the resizing the page view (e.g. Fit Page or Fit Width) will show the correct page two ahead/behind.

This problem appeared when I upgraded from Ubuntu 8.10 to Ubuntu 9.04.

I have (at least) the following packages installed:
okular 4:4.2.2-0ubuntu2
okular-extra-backends 4:4.2.2-0ubuntu2
libokularcore1 4:4.2.2-0ubuntu2

The problem does not appear in Evince (2.26.1).
Comment 1 Pino Toscano 2009-05-02 15:10:55 UTC
Cannot reproduce.
Comment 2 Philip Stephenson 2009-05-05 06:35:22 UTC
I've just noticed that the problems I described seem only to exist with the View|Continuous is _not_ checked.
Comment 3 Pino Toscano 2009-05-25 16:44:53 UTC
Uhm, which version of Qt 4 do you have?
Comment 4 Philip Stephenson 2009-05-26 03:55:25 UTC
QT Version 4.5.0, default settings as installed from Ubuntu Jaunty 9.04 repository.

A few days ago, another problem started with okular.  When I attempt to start it, the okular window appears, without icons and text, and my system seizes up.  Crtl+Alt+Backspace does not restart the xserver, nor does Crtl+Alt+Delete shutdown system.  The only solution I have found is to switch off the power.  The problem is not associated with any particular file.  Happens when okular is opened on its own.  I've since uninstalled okular; making do with Evince and Adobe Reader, neither of which is a patch on the okular I remember with Ubuntu 8.10.
Comment 5 sphakka 2011-09-28 14:28:56 UTC
Hi there,

This also happens to me when using PgUp/Down keys in _continuous_ mode: every now and then, at first PgDown hit, the screen flickers but the page doesn't change. I also noticed that sometimes the window seems to lose its keyboard focus and I need to click in it in order to regain control; this happens f.i. after pointing to the menu bar and releasing the focus on it:

0) open a PDF in Okular;
1) select "Continuous" mode via the keyboard -- Alt + v + c: keyboard control is lost, need to click with mouse to get it back. Same problem then:
2) focus on menu bar and release via the keyboard -- Alt + [FEB...], ESC, ESC: keyboard control lost, mouse click to get it back.

Running on Gentoo with:
- KDE/Okular v4.6.5
- Qt v4.7.2-r2

Cheers,

  ^s
Comment 6 sphakka 2011-09-28 14:59:34 UTC
Further info.

1) Forget about the keyboard focus problem: it happens even if "Continuous" is not selected, though a third ESC always gives back control to the keyboard. So I guess this is a global KDE "feature" ;-).
2) PgUp works fine irrespective of "Continuous" and/or "Trim margins" modes. 
3) PgDown:
- in normal mode (no continuous, no trim): scrolls correctly one page though often jerkily (slow page load/refresh?);
- in "Continuous" + "Trim margins" mode: misses a scroll every 2-5 hits, enough to be irritating. This happens irrespective of the memory usage setting.

Maybe the weird PgDown behaviour depends on bad forward page caching?

^s
Comment 7 jordonwii 2011-12-22 23:22:06 UTC
I'm unable to reproduce on Okular 0.13.3, KDE 4.7.3. I'm using continuous mode, and hitting any of Previous/Next or Pg-Up/Pg-Down works fine. 

If you are still having the issue, please post here and provide an example PDF.
Comment 8 Myriam Schweingruber 2011-12-27 17:24:20 UTC
Changing status accordingly. I can't reproduce this either, using Okular 0.13.80
Comment 9 sphakka 2011-12-27 22:18:29 UTC
Hi,

(In reply to comment #7)
> I'm unable to reproduce on Okular 0.13.3, KDE 4.7.3. I'm using continuous mode,
> and hitting any of Previous/Next or Pg-Up/Pg-Down works fine. 
> 
> If you are still having the issue, please post here and provide an example PDF.

You also need to enable "Trim Margins" Try this, f.i.:
<http://ctan.mirrorcatalogs.com/obsolete/macros/latex/contrib/subfigure/subfigure.pdf>

Now with Okular 0.13.3, KDE 4.7.3, PgDown misses almost always one hit out of two (~50%), so worse than before though more predictable. The same now happens with PgUp. Steps to reproduce:

0) open the document (it should start at its first page);
1) hit PgDown repeatedly and slowly enough to see the artifact: the first or second hit makes the page flicker (no scroll), a subsequent one scrolls down correcly;
2) now go back with "Ctrl+Home" and start over again scrolling down with PgDown: no problem until you get to the last visited page, then it'll flicker again one PgDown hit out two.

The same happens with PgUp if you start from the bottom by hitting "Ctrl+End", then scroll up. Anyways, if the *whole* document is visited in either directions, Okular will scroll perfectly from then on.

Cheers,

  ^s