GNOME Bugzilla – Bug 461236
crash in Text Editor: When I try to use SKK to...
Last modified: 2007-07-28 14:28:50 UTC
Version: 2.18.2 What were you doing when the application crashed? When I try to use SKK to write document and close geditor. Distribution: Unknown Gnome Release: 2.18.3 2007-07-27 (FreeBSD GNOME Project) BugBuddy Version: 2.18.1 System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #2: Sat Mar 31 23:37:31 JST 2007 nakano@aptiva720.nifty.com:/usr/src/sys/i386/compile/MYKERNEL i386 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 49296 vsize: 49296 resident: 29892 share: 46347952 rss: 29892 rss_rlim: 7473 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 100167] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100167] 0x2912e6cd in wait4 () from /lib/libc.so.6
+ Trace 151178
Thread 1 (LWP 100167)
Output of custom script "/usr/local/lib/gedit-2/gedit-bugreport.sh": Active plugins: No plugin installed in $HOME. Module versions: - 2.12.12 - 2.10.13 - 1.8.5 - 2.18.1 - 2.6.1 - 2.18.0 - 2.18.1 - 2.12.3 - 2.10.6 - 2.18.2 - 2.18.0 - 1.3.0 - 0.58 Python module versions: - python 2.4.4 - pygtk 2.10.6 (GTK+ 2.10.13) - gnome-python 2.18.2 ----------- .xsession-errors --------------------- Loading socket FrontEnd module ... Starting SCIM as daemon ... GTK Panel of SCIM 1.4.7 (gedit:2098): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed Launching a SCIM daemon with Socket FrontEnd... Loading simple Config module ... Creating backend ... Loading socket FrontEnd module ... Starting SCIM as daemon ... GTK Panel of SCIM 1.4.7 warning: Unable to get location for thread creation breakpoint: generic error --------------------------------------------------
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 ***