Bug 984039

Summary: ibus-libpinyin using 100% cpu
Product: [Fedora] Fedora Reporter: Luiz Corte Real <sr.saude>
Component: ibus-libpinyinAssignee: Peng Wu <pwu>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: i18n-bugs, leetnux, petersen, pwu, sr.saude
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: ibus-libpinyin-1.6.91-2.fc18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-02 03:23:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ibus-libpinyin backtrace when unresponsive
none
My table.conf none

Description Luiz Corte Real 2013-07-12 15:24:01 UTC
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

Comment 1 Peng Wu 2013-07-15 04:47:58 UTC
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.

Comment 2 Luiz Corte Real 2013-07-19 13:06:25 UTC
Created attachment 775800 [details]
ibus-libpinyin backtrace when unresponsive

Comment 3 Peng Wu 2013-07-22 02:39:48 UTC
Please upload the "/usr/lib64/libpinyin/data/table.conf" to analyze this bug.

BTW, which arch are you using?

Comment 4 Peng Wu 2013-07-26 03:38:59 UTC
Do you also use Germany Locale/Format?

Comment 5 Peng Wu 2013-07-26 04:42:05 UTC
Or other locales, which don't use "0.276607" as the numeric format?

Comment 6 Peng Wu 2013-07-30 05:37:13 UTC
*** Bug 988408 has been marked as a duplicate of this bug. ***

Comment 7 Fedora Update System 2013-07-30 07:51:13 UTC
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

Comment 8 Fedora Update System 2013-07-30 07:51:24 UTC
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

Comment 9 Luiz Corte Real 2013-07-30 13:47:47 UTC
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)

Comment 10 Fedora Update System 2013-08-02 03:23:21 UTC
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.

Comment 11 Fedora Update System 2013-08-02 03:42:41 UTC
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.