GNOME Bugzilla – Bug 324886
Evince crashes upon highlighting
Last modified: 2005-12-23 19:18:11 UTC
Distribution: Fedora Core release 4 (Stentz) Package: evince Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Evince crashes upon highlighting Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Evince will crash if you try to highlight text upon changing window focus Steps to reproduce the crash: 1. open a pdf with evince 2. open and play in a terminal 3. click in some text in the evince window and keeping the mouse pressed down try to highlight text Expected Results: it highlights the text How often does this happen? everytime for me Additional Information: 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 -1208289600 (LWP 12467)] [New Thread -1210389584 (LWP 12468)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00cd6402 in __kernel_vsyscall ()
+ Trace 64782
Thread 1 (Thread -1208289600 (LWP 12467))
------- Bug created by bug-buddy at 2005-12-23 16:54 -------
Thanks a lot for reporting, this problem should be fixed in poppler 0.4.3 *** This bug has been marked as a duplicate of 315552 ***