Bug 984039 - ibus-libpinyin using 100% cpu
Summary: ibus-libpinyin using 100% cpu
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-libpinyin
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peng Wu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 988408 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-12 15:24 UTC by Luiz Corte Real
Modified: 2013-08-02 03:42 UTC (History)
5 users (show)

Fixed In Version: ibus-libpinyin-1.6.91-2.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-02 03:23:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ibus-libpinyin backtrace when unresponsive (4.67 KB, text/plain)
2013-07-19 13:06 UTC, Luiz Corte Real
no flags Details
My table.conf (602 bytes, text/plain)
2013-07-30 13:47 UTC, Luiz Corte Real
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.