GNOME Bugzilla – Bug 321232
Evince crashes when during drag&drop
Last modified: 2005-11-11 18:04:48 UTC
Distribution: Fedora Core release 4 (Stentz) Package: evince Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Evince crashes when during drag&drop Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Evince crashes when you click inside the evince window and move your mouse without releasing the button (Drag&Drop). Steps to reproduce the crash: 1. Open any document 2. Click on the document 3. Move the mouse (without releasing the mouse) Expected Results: I don't know but this should not crash the application How often does this happen? Everytime Additional Information: evince-0.4.0-1.2 WindowMaker-0.92.0-3.fc4 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 -1209178432 (LWP 8025)] [New Thread -1211511888 (LWP 8026)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00839402 in __kernel_vsyscall ()
+ Trace 64011
Thread 1 (Thread -1209178432 (LWP 8025))
------- Bug moved to this database by unknown@gnome.bugs 2005-11-11 14:27 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 Anthony-Ferrand@numericable.fr.
Thanks for reporting this, that particular problem is already tracked. Feel free to report any other problem you'll find. *** This bug has been marked as a duplicate of 317294 ***