GNOME Bugzilla – Bug 322124
Evince crashed for no apparent reason
Last modified: 2005-11-24 08:46:53 UTC
Distribution: Ubuntu 5.10 (breezy) Package: evince Severity: critical Version: GNOME2.12.1 unspecified Gnome-Distributor: Ubuntu Synopsis: Crashed for no apparent reason Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: No warning, just died, no apparent explanation Steps to reproduce the crash: 1. Open a specific PDF file 2. just clicking around, dragging to select text 3. crash Expected Results: Shouldn't crash! How often does this happen? Occasionally, I think something similar happened with a different file, but don't remember Additional Information: Sorry for any vagueness, hopefully this report isn't entirely useless. Debugging Information: Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' 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) (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) [Thread debugging using libthread_db enabled] [New Thread -1228253504 (LWP 3809)] [New Thread -1230099536 (LWP 3810)] (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 64188
Thread 1 (Thread -1228253504 (LWP 3809))
------- Bug moved to this database by unknown@gnome.bugs 2005-11-22 12:15 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 craig.marshall@oxfordint.co.uk.
Thanks for reporting this. It's annoying poppler bug that needs to be fixed. Hope, we'll solve this problem soon. *** This bug has been marked as a duplicate of 315552 ***