libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-chewing --ibus comment: I was typing traditional Chinese with ibus-chewing and activating / un-activating ibus with CTRL-Space in the proprietary Google Chrome build on the Google+ website and ibus-engine-chewing somehow crashed. crash_function: __GI_raise executable: /usr/libexec/ibus-engine-chewing kernel: 3.1.0-7.fc16.x86_64 pid: 31148 pwd: /tmp reason: Process /usr/libexec/ibus-engine-chewing was killed by signal 6 (SIGABRT) time: Sat 10 Dec 2011 03:59:18 AM CST uid: 500 username: scottt xsession_errors: backtrace: Text file, 20234 bytes build_ids: Text file, 2665 bytes dso_list: Text file, 6276 bytes maps: Text file, 164522 bytes smolt_data: Text file, 2792 bytes environ: :SHELL=/bin/bash :DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-Fy8ROutbqs,guid=9de904bbd90bee778416721100000013 :XDG_SESSION_COOKIE=2321847de248bbc0238e912600000004-1320874087.662970-627674432 :XDG_RUNTIME_DIR=/run/user/scottt :DISPLAY=:0 :DESKTOP_SESSION=gnome :SSH_AUTH_SOCK=/tmp/keyring-4gVTjR/ssh :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2142,unix/unix:/tmp/.ICE-unix/2142 :WINDOWPATH=1 :PATH=/usr/local/bin:/usr/bin:/bin :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :GDMSESSION=gnome :XDG_VTNR=1 :USERNAME=scottt :XDG_SESSION_ID=2 :GPG_AGENT_INFO=/tmp/keyring-4gVTjR/gpg:0:1 :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Fy8ROutbqs,guid=9de904bbd90bee778416721100000013 :XDG_SEAT=seat0 :XAUTHORITY=/var/run/gdm/auth-for-scottt-ublKgk/database :USER=scottt :DBUS_STARTER_BUS_TYPE=session :GNOME_KEYRING_PID=2137 :SHLVL=1 :PWD=/home/scottt :GNOME_KEYRING_CONTROL=/tmp/keyring-4gVTjR :LANG=en_US.UTF-8 :_=/usr/bin/dbus-launch :LOGNAME=scottt :HOME=/home/scottt :LC_CTYPE=en_US.UTF-8 :GTK_IM_MODULE=ibus :QT_IM_MODULE=xim :XMODIFIERS=@im=ibus var_log_messages: :Dec 5 02:33:24 sd dbus-daemon[958]: (packagekitd:9074): PkPlugin-DEBUG: adding /usr/libexec/ibus-engine-chewing pid:31148 uid:500 :Dec 6 21:19:49 sd dbus-daemon[958]: (packagekitd:32360): PkPlugin-DEBUG: adding /usr/libexec/ibus-engine-chewing pid:31148 uid:500 :Dec 10 03:59:18 sd abrt[7817]: File '/usr/libexec/ibus-engine-chewing.#prelink#.xjbd6C' seems to be deleted :Dec 10 03:59:18 sd abrt[7817]: File '/usr/libexec/ibus-engine-chewing.#prelink#.xjbd6C' seems to be a prelink temporary file :Dec 10 03:59:19 sd abrt[7817]: Saved core dump of pid 31148 (/usr/libexec/ibus-engine-chewing) to /var/spool/abrt/ccpp-2011-12-10-03:59:18-31148 (107511808 bytes)
Created attachment 544945 [details] File: dso_list
Created attachment 544946 [details] File: build_ids
Created attachment 544947 [details] File: smolt_data
Created attachment 544948 [details] File: maps
Created attachment 544949 [details] File: backtrace
*** Bug 795762 has been marked as a duplicate of this bug. ***
Seems like your libchewing is broken, would you mind reinstall libchewing again? Thanks!
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Hi Scott: Please try following command: ls -l /usr/share/chewing/ph_index.dat Mine returns: -rw-r--r--. 1 root root 474904 2010-03-05 15:05 /usr/share/chewing/ph_index.dat How about yours?
$ ls -l /usr/share/chewing/ph_index.dat ls: cannot access /usr/share/chewing/ph_index.dat: No such file or director $ ls -l /usr/lib64/libchewing/ph_index.dat -rw-r--r--. 1 root root 477012 Feb 27 2013 /usr/lib64/libchewing/ph_index.dat Note that I filed this bug while Fedora 16 was the current release. I've updated my Fedora install multiple times since and the above output is from Fedora 19.
Thanks for the reply. Have you experience something similar in Fedora 19? Specifically, whether libchewing-0.3.4 solved this issue? Regards,
(In reply to Ding-Yi Chen from comment #12) I can't reproduce this now. I don't think the root cause is necessarily fixed pease but feel free to close this bug.
Thanks for the reply, since both of us cannot reproduce the bug, I hereby close this bug as WORKFORME. Please reopen this bug if you encounter the same bug again. Regards,
*** Bug 866522 has been marked as a duplicate of this bug. ***
Then again, this maybe introduced by libchewing-0.3.3-3 which trying to solve multilib conflict. However this might be already fixed in libchewing-0.3.4-2.
*** Bug 874356 has been marked as a duplicate of this bug. ***