GNOME Bugzilla – Bug 491623
crash in Text Editor: just close the gedit's m...
Last modified: 2007-10-30 11:33:53 UTC
Version: 2.18.2 What were you doing when the application crashed? just close the gedit's main window Distribution: Unknown Gnome Release: 2.18.3 2007-09-16 (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: 66416 vsize: 66416 resident: 28696 share: 63073029 rss: 28696 rss_rlim: 7174 CPU usage: start_time: 0 rtime: 133 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 100131] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100131] 0x2914e6cd in wait4 () from /lib/libc.so.6
+ Trace 173843
Thread 1 (LWP 100131)
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 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 ***