GNOME Bugzilla – Bug 318028
Evince crashes when reloading a slightly modified PDF file
Last modified: 2005-10-05 15:29:33 UTC
Distribution: Fedora Core release 4 (Stentz) Package: evince Severity: critical Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Evince crashes when reloading a slightly modified PDF file Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Evince crashes when reloading a slightly modified PDF file with Ctrl-R Steps to reproduce the crash: 1. open evince on a PDF file 2. modify the PDF file with some software like FOP 3. reload the already open file Expected Results: Normally it works, but sometimes, evince crashes How often does this happen? once each 6 times? Additional Information: ghostview did more or less the same Debugging Information: Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208969536 (LWP 8478)] [New Thread -1211171920 (LWP 8479)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00c70402 in ?? ()
+ Trace 63380
Thread 1 (Thread -1208969536 (LWP 8478))
------- Bug moved to this database by unknown@gnome.bugs 2005-10-05 15:24 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was pf@arenberg.cc.
Hello. Thanks for reporting this. I think it's a duplicate and it should be fixed in CVS. Feel free to report about any other problem you'll find. *** This bug has been marked as a duplicate of 314986 ***