Version: 0.6 (using 4.00.00 (KDE 4.0.0) "release 2.2", compiled sources) Compiler: gcc OS: Linux (i686) release 2.6.22.13-0.3-default If you scroll down (or up) with PgDn key or arrow button the page is changed, but moves down a little bit (using page fit the screen). This way after few clicks the page is in its half (and further), not fiting the screen any more. This bug also existed in kpdf.
Just noticed that it now happens when okular is maximized, if the window is smaller then the problem does not seem to appear.
> If you scroll down (or up) with PgDn key or arrow button Well, using PgDown or the Down arrow key is different, I think you mean just with the PgUp/Down keys? Hmm, cannot reproduce here, selecting the "Fit to Page" zoom option and then scrolling up/down with PgUp/Down always display the current page, centered. (The KPDF bug you refer to is bug #107996, no?)
I mean the PgDown key and right arrow button (in toolbar). The bug #107996 looks like the same issue, correct.
Interestingly enough, in kpdf it's much worse, the unwanted scroll is much higher than in okular. And unlike in kpdf in okular it at least works OK if the window is not maximized. Is there anything I could do to debug this further?
Hmm, tested it again and now for one pdf it's broken independent of if the windows is maximized and not and for another pdf it's broken only if not maximized. I updated okular from kde4 openSUSE buildservice repo, but it looks only some libraries have changed, not okular. I'll try to find some more (public) PDF files on which it's reproducible.
Created attachment 23334 [details] pdf file showing the behavior for me With this file the problem is shown independent of the window size.
The packages installed, if that matters: libpoppler2-0.6.1-6.1 libpoppler-qt4-2-0.6.1-6.1 kde4-okular-4.0-18.2
It seems to work well now, with okular 0.7.2 (kde 4.1.2).
So should this be closed?
*** This bug has been marked as a duplicate of bug 180263 ***
(Sorry, marked as dupe in the other way round...)
*** Bug 180263 has been marked as a duplicate of this bug. ***
I have not seen this in a while so I would say it is fixed now. Has anybody experienced this behavior with any recent okular version?
This bug has been quiet in a while, and Michal couldn't reproduce it nine months ago. I also tried it just now and don't see it with 0.12.2. Is this still an issue for the original commiter? If not, we can close the bug.
I believe I still sometimes see this behavior with 0.12.x, but I can't recall anything specific as of now so this could be probably closed.