GNOME Bugzilla – Bug 480459
crash in Text Editor: Close a document.
Last modified: 2007-12-25 11:40:39 UTC
Version: 2.18.2 What were you doing when the application crashed? Close a document. Distribution: Unknown Gnome Release: 2.18.3 2007-09-05 (FreeBSD GNOME Project) BugBuddy Version: 2.18.1 System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP i386 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 43720 vsize: 43720 resident: 25520 share: 40926726 rss: 25520 rss_rlim: 6380 CPU usage: start_time: 0 rtime: 266 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133 Backtrace was generated from '/usr/local/bin/gedit' (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)...[New LWP 100202] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100202] 0x291836cd in wait4 () from /lib/libc.so.6
+ Trace 165541
Thread 1 (LWP 100202)
Output of custom script "/usr/local/lib/gedit-2/gedit-bugreport.sh": Active plugins: No plugin installed in $HOME. Module versions: - 2.12.13 - 2.10.14 - 1.8.5 - 2.18.1 - 2.6.2 - 2.18.0 - 2.18.1 - 2.12.3 - 2.10.6 - 2.18.2 - 2.18.0 - 1.3.0 - 1.4 Python module versions: - python 2.5.1 - pygtk 2.10.6 (GTK+ 2.10.14) - gnome-python 2.18.2
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for gedit, gtk, glib, gnome-vfs, libgnome, libgnomeui, pango and gtksourceview (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Possible duplicate of Bug 346444?
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 346444 ***