Description of problem: When activating pinyin input using GNOME's widget in the status bar, the process ibus-engine-lib starts but eats 100% cpu. Also, trying to type any text doesn't work (it doesn't show the character selection window). Version-Release number of selected component (if applicable): 1.6.91-1.fc19 How reproducible: Always happens when I activate it Steps to Reproduce: 1. Click on the input selection method widget 2. Choose "Chinese (Intelligent Pinyin)" Actual results: 100% cpu usage and no pinyin input Expected results: Typing pinyin and seeing a list of chinese characters to choose from
Could you use gdb to post the back trace of the ibus-engine-libpinyin? 1. run $gdb attach `pidof /usr/libexec/ibus-engine-libpinyin` 2. use 'where' to get the back trace, and post it here.
Created attachment 775800 [details] ibus-libpinyin backtrace when unresponsive
Please upload the "/usr/lib64/libpinyin/data/table.conf" to analyze this bug. BTW, which arch are you using?
Do you also use Germany Locale/Format?
Or other locales, which don't use "0.276607" as the numeric format?
*** Bug 988408 has been marked as a duplicate of this bug. ***
ibus-libpinyin-1.6.91-2.fc18,libpinyin-0.9.93-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ibus-libpinyin-1.6.91-2.fc18,libpinyin-0.9.93-2.fc18
ibus-libpinyin-1.6.91-2.fc19,libpinyin-0.9.93-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ibus-libpinyin-1.6.91-2.fc19,libpinyin-0.9.93-2.fc19
Created attachment 780671 [details] My table.conf Sorry for the delay. This is my table.conf. Also, yes, I use a locale where 0.297 is not separated by . (I use the french locale)
ibus-libpinyin-1.6.91-2.fc19, libpinyin-0.9.93-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
ibus-libpinyin-1.6.91-2.fc18, libpinyin-0.9.93-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.