GNOME Bugzilla – Bug 152544
Gedit crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: gedit Severity: normal Version: GNOME2.6.1 2.6.2 Gnome-Distributor: Debian Synopsis: Gedit crash Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.2 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Gedit crashes with a message "gEdit has quit unexpectedly. Steps to reproduce the crash: 1. Open one of the recent files in recent file list. 2. Try opening another file by clicking "Open" button 3. Crash... :( Expected Results: How often does this happen? Now it happens every time since I upgraded my Debian box with apt-get upgrade. Additional Information: This happens only with one text file in a recent-file list. I cannot reproduce the error when I open another file. 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 1092994304 (LWP 1355)] [New Thread 1109154736 (LWP 2537)] [Thread debugging using libthread_db enabled] [New Thread 1092994304 (LWP 1355)] [New Thread 1109154736 (LWP 2537)] [Thread debugging using libthread_db enabled] [New Thread 1092994304 (LWP 1355)] [New Thread 1109154736 (LWP 2537)] (no debugging symbols found)...[New Thread 1108892592 (LWP 2536)] (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)...(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)...0x4092a431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 50112
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-13 17:13 ------- Unknown version 2.6.2 in product gedit. Setting version to "0.5.1". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gedit". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was trubin@osuosl.org. 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.
Unique stack trace.
*** Bug 152703 has been marked as a duplicate of this bug. ***
Thanks for the bug report. I cannot reproduce the crash you have described in gedit 2.8.0. Unfortunately, the attached 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.
trubin: please, upgrade to the newest version of gedit and let us know if you are still able to reproduce the crash you reported.
It seems a crash in the new gtk+ file chooser... Chaging product to gtk+
A little bit different trace of crush... May be this will help. 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)...[Thread debugging using libthread_db enabled] [New Thread 1088931072 (LWP 20841)] [New Thread 1105111984 (LWP 20843)] [Thread debugging using libthread_db enabled] [New Thread 1088931072 (LWP 20841)] [New Thread 1105111984 (LWP 20843)] [Thread debugging using libthread_db enabled] [New Thread 1088931072 (LWP 20841)] [New Thread 1105111984 (LWP 20843)] [New Thread 1104849840 (LWP 20842)] 0x40549431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 50389
Which version of gtk+,libgnomeui, gnome-vfs and gedit are you using?
*** Bug 153720 has been marked as a duplicate of this bug. ***
*** Bug 154400 has been marked as a duplicate of this bug. ***
*** Bug 154445 has been marked as a duplicate of this bug. ***
Versions: GTK+ : 2.4.10-1 libgnomeui : 2.6.1.1-4 gnome-vfs : 1.0.5-5 gedit : 2.6.2-1
Paolo, Alright, I was able to reproduce the bug in gedit 2.8.0 I compiled the source files using instructions that came with the tarball. When I run gedit from the command line, then the following message appear after loading, but it does not cause the crash: "*** attempt to put segment in horiz list twice" A new stack trace looks like this: Backtrace was generated from '/usr/local/bin/gedit' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1088935104 (LWP 2109)] [New Thread 1104624560 (LWP 2111)] [Thread debugging using libthread_db enabled] [New Thread 1088935104 (LWP 2109)] [New Thread 1104624560 (LWP 2111)] [Thread debugging using libthread_db enabled] [New Thread 1088935104 (LWP 2109)] [New Thread 1104624560 (LWP 2111)] [New Thread 1104362416 (LWP 2110)] 0x407f9431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 50905
*** Bug 156309 has been marked as a duplicate of this bug. ***
*** Bug 156315 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 151715 ***
*** Bug 157717 has been marked as a duplicate of this bug. ***