libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-chewing --ibus crash_function: __GI_raise executable: /usr/libexec/ibus-engine-chewing kernel: 3.1.1-2.fc16.x86_64 pid: 1844 pwd: /tmp reason: Process /usr/libexec/ibus-engine-chewing was killed by signal 6 (SIGABRT) time: 西元2011年11月23日 (週三) 00時21分42秒 uid: 1000 var_log_messages: Nov 23 00:21:49 HiHeHo-S205 abrt[9503]: Saved core dump of pid 1844 (/usr/libexec/ibus-engine-chewing) to /var/spool/abrt/ccpp-2011-11-23-00:21:41-1844 (199221248 bytes) xsession_errors: backtrace: Text file, 20712 bytes build_ids: Text file, 2870 bytes dso_list: Text file, 7841 bytes maps: Text file, 140859 bytes comment: :I am using Ctrl + Space to turn on and turn of ibus-chewing for many times in empathy Conversation dialogue to type English and Chinese both. :All of a sudden, there is no responce with ibus-chewing. :After a while, ABRT tells me that ibus-chewing is crashed. environ: :SHELL=/bin/bash :DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-wX2tOVmDko,guid=21703255d3b59c5997807ae80000002c :XDG_SESSION_COOKIE=1e82553158d486ff2e6989dc00000011-1321970568.747148-830253820 :XDG_RUNTIME_DIR=/run/user/username :DISPLAY=:0 :DESKTOP_SESSION=gnome :WINDOWPATH=1 :PATH=/usr/local/bin:/usr/bin:/bin :GDMSESSION=gnome :XDG_VTNR=1 :USERNAME=username :XDG_SESSION_ID=2 :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-wX2tOVmDko,guid=21703255d3b59c5997807ae80000002c :XDG_SEAT=seat0 :XAUTHORITY=/var/run/gdm/auth-for-username-OuppXe/database :USER=username :DBUS_STARTER_BUS_TYPE=session :GNOME_KEYRING_PID=1204 :SHLVL=1 :PWD=/home/username :GNOME_KEYRING_CONTROL=/tmp/keyring-sAfNMJ :LANG=zh_TW.UTF-8 :_=/usr/bin/dbus-launch :LOGNAME=username :HOME=/home/username :LC_CTYPE=zh_TW.UTF-8 :GTK_IM_MODULE=ibus :QT_IM_MODULE=xim :XMODIFIERS=@im=ibus
Created attachment 535293 [details] File: maps
Created attachment 535294 [details] File: dso_list
Created attachment 535295 [details] File: build_ids
Created attachment 535296 [details] File: backtrace
Backtrace analysis found this bug to be similar to bug #795762, closing as duplicate. This comment is automatically generated. *** This bug has been marked as a duplicate of bug 795762 ***