GNOME Bugzilla – Bug 314033
Crashed when trying to open a file
Last modified: 2006-03-04 14:10:44 UTC
Distribution: Fedora Core release 4 (Stentz) Package: gedit Severity: Normal Version: GNOME2.11.90 2.10.4 Gnome-Distributor: Red Hat, Inc Synopsis: Crashed when trying to open a file Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.10.4 BugBuddy-GnomeVersion: 2.0 (2.11.2) Description: Description of the crash: I was attempting to open a file - I selected File->Open and gedit died. Steps to reproduce the crash: 1. open gedit with some files on the command line 2. Select File->Open Expected Results: File open dialog should appear. How often does this happen? Unknown at this time - this is the first incident. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gedit' (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) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208805712 (LWP 30718)] [New Thread -1325442128 (LWP 30744)] [New Thread -1325098064 (LWP 30743)] [New Thread -1324831824 (LWP 30742)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 62566
Thread 1 (Thread -1208805712 (LWP 30718))
------- Bug moved to this database by unknown@gnome.bugs 2005-08-20 14:35 UTC ------- Unknown version 2.10.4 in product gedit. Setting version to "2.10.x".
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!