GNOME Bugzilla – Bug 160610
Crash while trying to save in GEdit
Last modified: 2005-02-28 17:09:28 UTC
Distribution: Debian 3.1 Package: gedit Severity: normal Version: 2.6.2 Synopsis: Crash while trying to save in GEdit Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.2 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: I tried to save a file in GEdit. It crashed instead. Stack trace should be included if bug-buddy does its thing. 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)...(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 1085193216 (LWP 3435)] [New Thread 1109674928 (LWP 19814)] [Thread debugging using libthread_db enabled] [New Thread 1085193216 (LWP 3435)] [New Thread 1109674928 (LWP 19814)] [Thread debugging using libthread_db enabled] [New Thread 1085193216 (LWP 3435)] [New Thread 1109674928 (LWP 19814)] (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)...0x4118a431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 53229
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-06 14:58 ------- Unknown version 2.6.2 in product gedit. Setting version to "2.6.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gedit". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 151715 ***
pbor: are you sure this is a duplicate of bug 151715. It seems to have a different stack trace. Nathan: thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. Which version of gtk+, libgnome, libgnomeui and gedit are you using? If you are using libgnomeui 2.6.x (x < 2), please, try to see if there is an available update for 2.6.y (y >= 2).
oops sorry I should have looked more closely, but we get so much dups of that bug... However note that it's still probably a dup since Debian with gedit-2.6 is one of the typical configurations affected by 151715, the crash happened while trying to save and gnomevfs seems to be involved looking at the little that could be read from the current stack trace.
Sorry the stack trace came out as crap. Debian seems to strip their binaries, which is good for disk space, but makes bug-buddy somewhat less useful. I would be happy to recompile from source, but as I can't reproduce the bug, I'm not sure how helpful that would be. Here are the package versions you requested: ii libgtk2.0-0 2.4.13-1 The GTK+ graphical user interface library ii libgnome2-0 2.8.0-5 The GNOME 2 library - runtime files ii libgnomeui-0 2.8.0-3 The GNOME 2 libraries (User Interface) - run ii gedit 2.6.2-1 light-weight text editor This is what I had done when the crash occured: Gedit was loaded by the session manager with the last file I had edited. I had some text I wanted to save from gnome-terminal, so I selected it, created a new tab in gedit, and pasted it with the middle mouse button. I then hit the save button, and the program crashed.
This is not a duplicate of bug #151715 since the version of libgnomeui is not 2.6.x (AFAIK, 2.8.0 does not have such problem). Unfortunately, the attached stack trace is not very useful in determining the cause of the crash. I will try to reproduce it following the steps you reported in your last comment.
I have tried to reproduce this bug following the steps described by the reported, but gedit didn't crash. Since it is not possible to determine the cause of the crash from the attached stack trace, I'm closing this bug as INCOMPLETE. Nathan: please, reopen it if you are still able to reproduce it and/or you have more info or a better stack trace.
I still can't reproduce the crash. I have no clue what happened.