Summary: | okular crashes when loading pdf file and scrolling at the same time | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Sebastian <sebi.auer> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Sebastian
2008-02-09 21:59:21 UTC
All files or a specific file? If it is a specific file can you please attach it? It seems to be with all pdf files. when do you use the scrollbar? When the document "closes" and you get a "Reloading document"? Before that? After that? it's hard to say, as it happens quite fast... maybe a little more background information could help: I'm starting pdflatex in konsole and while latex is still compiling (this sometimes can take some time), I am scrolling in okular to the position, where I expect made my new changes. So, when pdflatex has done its job (and has updated the pdf file => reloading sequence in okular is starting) and I'm still "scrolling around", okular crashes. I can't be sure, but I assume, okular first gets the signal "hey, someone updated your pdf file". Then it closes the file in order in order to reopen it. Reopening takes some time, so while okular is still busy, reopening the file, the progress bar signal of my scrolling action is causing some error, as it says "scroll up 5 lines, please" but there is nothing to scroll while loading. - But, as I said, it's just a guess! I just tried the same thing with good old kpdf and there weren't any problems. It seems (another guess, only!) that kpdf doesn't actually close/remove the pdf file before reloading. It just keeps the old version open, until the new version is fully available and can be replaced for the old one without any delay. Hoping, this helps you a bit. :) Can you still reproduce this bug with a recent version of KDE like 4.0.5 or 4.1 ? No response. If this is still a problem in a current version, please reopen with more information |