After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 171582 - rendering garbage when pdf file changed on disk
rendering garbage when pdf file changed on disk
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-25 12:48 UTC by Géry Debongnie
Modified: 2011-06-26 23:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Géry Debongnie 2005-03-25 12:48:17 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.
Comment 2 Nickolay V. Shmyrev 2005-05-15 18:11:52 UTC
It would be nice if evince will automatically reload document on changes. This
can be easily implemented with GnomeVfsMonitor.
Comment 3 Nickolay V. Shmyrev 2005-05-15 18:12:21 UTC
*** Bug 304249 has been marked as a duplicate of this bug. ***
Comment 4 Marco Pesenti Gritti 2005-05-15 18:27:52 UTC
I think there was discussion about automatic reloading in the reload bug... Cant
find it right now.
Comment 5 Kai Willadsen 2005-05-16 01:15:57 UTC
Reload was bug 165119.
Comment 6 Marco Pesenti Gritti 2005-07-26 12:51:12 UTC
Hmm not sure why this happen. Arent we loading the whole pdf on _load? Are we
accessing disk at all after that?
Comment 7 Martin Kretzschmar 2005-07-27 08:39:49 UTC
> Arent we loading the whole pdf on _load?

No

> Are we accessing disk at all after that?

Yes. That's how poppler works
Comment 8 Tobias Florek 2008-06-08 00:21:08 UTC
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)
Comment 9 Matt McCutchen 2008-09-14 02:26:52 UTC
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.
Comment 10 José Aliste 2011-06-26 23:09:24 UTC
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.