GNOME Bugzilla – Bug 330900
Crash in filepicker within Evince 0.4.0
Last modified: 2006-02-12 18:03:46 UTC
Distribution: Fedora Core release 4 (Stentz) Package: evince Severity: critical Version: GNOME2.10.0 0.4.x Gnome-Distributor: Red Hat, Inc Synopsis: Crash in filepicker within Evince 0.4.0 Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: 0.4.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Steps to reproduce the crash: 1. Open evince. 2. Press Ctrl+O to open a file. 3. Press Ctrl+L to type a filename in a mini-dialog spawned by the filepicker. 4. Type a path to a file, using Tab to autocomplete as desired. 5. Once the file is selected, hit Enter to dismiss the mini-dialog. 6. Crash Expected Results: The file should be opened or at least displayed the typed file in the filepicker. (The latter seems to be default GNOME behavior right now, with the former presumably being an unrelated bug.) How often does this happen? Consistently and reproducibly. If you're aware of and use the Ctrl+L workaround for not being able to type file names in the filepicker (ugh), this bug is incredibly annoying. It might possibly be a GTK bug, but I have only ever been able to reproduce this with evince, so I suspect the filepicker is somehow not being invoked correctly within evince code (although I have no proof; I attempted to debug this but encountered build issues with evince the two times I tried). 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) [Thread debugging using libthread_db enabled] [New Thread -1208633664 (LWP 27703)] [New Thread -1222128720 (LWP 27706)] [New Thread -1221862480 (LWP 27705)] [New Thread -1210733648 (LWP 27704)] 0x004dd402 in __kernel_vsyscall ()
+ Trace 66113
Thread 1 (Thread -1208633664 (LWP 27703))
------- Bug created by bug-buddy at 2006-02-12 17:21 -------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 317687 ***