GNOME Bugzilla – Bug 322418
Crash on opening a particular PDF
Last modified: 2005-12-22 22:52:34 UTC
Distribution: Fedora Core release 4 (Stentz) Package: evince Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Crash on opening a particular PDF Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Evince crashes when trying to open a particular PDF file. File URL is; http://www.freescale.com/files/microcontrollers/doc/app_note/AN1831.pdf Steps to reproduce the crash: 1. evince AN1831.pdf 2. 3. Expected Results: Should open PDF. Note that xpdf opens the file How often does this happen? Every time this file is opened. This is the only PDF file that I have seen this problem with Additional Information: Gnome evince 0.4.0 Fedora Core 4 xpdf version 3.01 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) `shared object read from target memory' has disappeared; keeping its symbols. (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 -1208756544 (LWP 8239)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 64251
Thread 1 (Thread -1208756544 (LWP 8239))
------- Bug moved to this database by unknown@gnome.bugs 2005-11-25 10:28 UTC -------
I cannot reproduce this with evince 0.4.0 on Ubuntu Breezy and that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Thank for reporting, this is a problem of fedora packaging. It should be fixed in newer versions. *** This bug has been marked as a duplicate of 313724 ***