GNOME Bugzilla – Bug 171582
rendering garbage when pdf file changed on disk
Last modified: 2011-06-26 23:09:24 UTC
Version details: 0.1.9 (ubuntu) Distribution/Version: Ubuntu Hoary 1. open any pdf file (containing more than 1 page) with evince. 2. change the pdf file (for example, compile a new file with latex) 3. go back to evince and change the page Result : the rendering is garbage. Result expected : I think evince should be able to explore the last version of the file. Or switch to the new file. Anyway, the current result is wrong.
Relevant Red Hat Bugs: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149139 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150384
It would be nice if evince will automatically reload document on changes. This can be easily implemented with GnomeVfsMonitor.
*** Bug 304249 has been marked as a duplicate of this bug. ***
I think there was discussion about automatic reloading in the reload bug... Cant find it right now.
Reload was bug 165119.
Hmm not sure why this happen. Arent we loading the whole pdf on _load? Are we accessing disk at all after that?
> Arent we loading the whole pdf on _load? No > Are we accessing disk at all after that? Yes. That's how poppler works
this still happens with evince 2.22. can evince not just scan the files mtime and reload, if this was before it was loaded? (i.e. compare the timestamps)
My makefile deletes the pdf file and writes a new one instead of rewriting the existing file in place. This approach seems to avoid confusing evince, since evince still has open the old, deleted file (which hasn't changed). Writing to a temporary file and renaming it into place would also work.
Marking as obsolete since for some time now we have been reloading the document when it is changed on disk, so the behaviour described in this bug does not apply anymore.