Version-Release number of selected component: ibus-libpinyin-1.7.2-1.fc22 Additional info: reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin::SubPhraseIndex::load executable: /usr/libexec/ibus-engine-libpinyin global_pid: 2633 kernel: 4.0.7-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 pinyin::SubPhraseIndex::load at phrase_index.cpp:349 #1 pinyin::FacadePhraseIndex::diff at phrase_index.cpp:273 #2 pinyin_save at pinyin.cpp:649 #3 PY::LibPinyinBackEnd::saveUserDB at PYLibPinyin.cc:374 #4 PY::LibPinyinBackEnd::timeoutCallback at PYLibPinyin.cc:362 #10 ibus_main at ibusshare.c:302 #11 start_component at PYMain.cc:141 Potential duplicate: bug 964577
Created attachment 1057571 [details] File: backtrace
Created attachment 1057572 [details] File: build_ids
Created attachment 1057573 [details] File: cgroup
Created attachment 1057574 [details] File: core_backtrace
Created attachment 1057575 [details] File: dso_list
Created attachment 1057576 [details] File: environ
Created attachment 1057577 [details] File: limits
Created attachment 1057578 [details] File: maps
Created attachment 1057579 [details] File: mountinfo
Created attachment 1057580 [details] File: namespaces
Created attachment 1057581 [details] File: open_fds
Created attachment 1057582 [details] File: proc_pid_status
Could you provide the tar ball of ~/.cache/ibus/libpinyin/ directory content?
Created attachment 1058298 [details] libpinyin tar ball
How frequently does this bug happen? Any special operations are performed on Fedora 22 before this bug happens, such as yum/dnf upgrade? Please provides the output of the following command: $ rpm -Va "libpinyin*"
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.