GNOME Bugzilla – Bug 319377
Crash on search
Last modified: 2005-10-21 14:32:58 UTC
From: <> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.12.1 Subject: Crash on search Distribution: Ubuntu 5.10 (breezy) Package: evince Severity: Normal Version: GNOME2.12.1 0.4.x Gnome-Distributor: Ubuntu Synopsis: Crash on search Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: 0.4.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: After seraching pdf-file evince crash. Steps to reproduce the crash: 1. Press ctrl-f and search any word. 2. Click into the document. 3. Sometimes it crashes, and sometime it keeps running. Expected Results: How often does this happen? Two times. Additional Information: I can't really reproduce the crash. I can only tell what I've done. 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 -1228327232 (LWP 8450)] [New Thread -1230464080 (LWP 8451)] (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 63645
Thread 1 (Thread -1228327232 (LWP 8450))
------- Bug moved to this database by unknown@gnome.bugs 2005-10-21 08:16 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 wspomer@web.de.
Thanks for reporting this, but this bug was already in our system. Feel free to file any other problem you'll find. *** This bug has been marked as a duplicate of 315553 ***
Ups, sorry.
*** This bug has been marked as a duplicate of 315552 ***