Red Hat Bugzilla – Bug 964577
[abrt] ibus-libpinyin-1.6.91-1.fc18: pinyin::SubPhraseIndex::load: Process /usr/libexec/ibus-engine-libpinyin was killed by signal 11 (SIGSEGV)
Last modified: 2014-06-17 08:16:41 EDT
Version-Release number of selected component: ibus-libpinyin-1.6.91-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus core_backtrace: crash_function: pinyin::SubPhraseIndex::load executable: /usr/libexec/ibus-engine-libpinyin kernel: 3.6.10-4.fc18.x86_64 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (7 frames) #0 pinyin::SubPhraseIndex::load at phrase_index.cpp:273 #1 pinyin::FacadePhraseIndex::diff at phrase_index.cpp:231 #2 pinyin_save at pinyin.cpp:423 #3 PY::LibPinyinBackEnd::saveUserDB at PYLibPinyin.cc:261 #4 PY::LibPinyinBackEnd::timeoutCallback at PYLibPinyin.cc:249 #10 ibus_main at ibusshare.c:295 #11 start_component at PYMain.cc:152
Created attachment 749919 [details] File: backtrace
Created attachment 749920 [details] File: cgroup
Created attachment 749921 [details] File: dso_list
Created attachment 749922 [details] File: environ
Created attachment 749923 [details] File: limits
Created attachment 749924 [details] File: maps
Created attachment 749925 [details] File: open_fds
Created attachment 749926 [details] File: proc_pid_status
Created attachment 749927 [details] File: var_log_messages
Please provides the result of the following commands: $ rpm -qa "libpinyin*" "ibus-libpinyin*" $ rpm -Va "libpinyin*" "ibus-libpinyin*"
I think I have the same problem, whenever I try to start pinyin input I get a huge process load. For me the outputs are: $ rpm -qa "libpinyin*" "ibus-libpinyin*" libpinyin-0.9.91-1.fc18.x86_64 libpinyin-data-0.9.91-1.fc18.x86_64 ibus-libpinyin-1.6.91-1.fc18.x86_64 $ rpm -Va "libpinyin*" "ibus-libpinyin*" does not return anything
(In reply to joh.sauer from comment #11) Could you use 'top' to check which process make the huge load? But I think his problem is not a huge load, but a crash. Does ibus-libpinyin also crash on your machine?
Could you send your personal data to me in ~/.cache/ibus by email, to analyze the problem?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.