GNOME Bugzilla – Bug 151560
Crash in file selector using gedit
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: gedit Severity: normal Version: 2.6.2 Synopsis: Crash in file selector using gedit Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.2 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: When I choose Save As from the menu in gedit after first having performed the below steps, gedit crashes. From the backtrace it looks like the crash happens in gtk+. Steps to reproduce the crash: 1. Download and unpack the following tarball: http://www.freakysoft.de/html/libkarma/libkarma-0.0.1.tar.gz 2. Go to the unpacked directory libkarma-0.0.1 in Nautilus. 3. Double-click on a file, such as karma.h so it opens in gedit. 4. Press "New" in gedit so a blank tab opens. 5. Choose "Save As" from the menu. Result: Gedit crashes before the file picker even shows up. The stacktrace seams to point to GTK+. How often does this happen? Every time I try the above steps. Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1093901312 (LWP 8385)] [New Thread 1107307440 (LWP 8387)] [Thread debugging using libthread_db enabled] [New Thread 1093901312 (LWP 8385)] [New Thread 1107307440 (LWP 8387)] [New Thread 1107045296 (LWP 8386)] [Thread debugging using libthread_db enabled] [New Thread 1093901312 (LWP 8385)] [New Thread 1107307440 (LWP 8387)] 0x40930431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 49792
I guess this could be the same bug as bug 139249, but I wanted to report it anyway since these steps cause the crash 100% of the time for me.
FWIW, I cannot reproduce this...
Please tell us your GTK+ version. The gedit version isn't helpful :-)
Oops, sorry Owen. I'm using gtk+ version 2.4.9 (official Debian packages).
*** This bug has been marked as a duplicate of 151715 ***