[Fedora-i18n-bugs] [Bug 586292] New: pinyin keep crash when CPU load high.

bugzilla at redhat.com bugzilla at redhat.com
Tue Apr 27 08:59:29 UTC 2010


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: pinyin keep crash when CPU load high.

https://bugzilla.redhat.com/show_bug.cgi?id=586292

           Summary: pinyin keep crash when CPU load high.
           Product: Red Hat Enterprise Linux 6
           Version: 6.0
          Platform: i686
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: low
         Component: ibus-pinyin
        AssignedTo: phuang at redhat.com
        ReportedBy: phuang at redhat.com
         QAContact: desktop-bugs at redhat.com
                CC: eng-i18n-bugs at redhat.com, phuang at redhat.com,
                    i18n-bugs at lists.fedoraproject.org, biaji.cn at gmail.com
        Depends on: 552445
             Group: rhel_beta
    Classification: Red Hat
    Target Release: ---
          Clone Of: 552445


+++ This bug was initially created as a clone of Bug #552445 +++

Description of problem:

Can't use pinyin input method when in high cpu load condition. Pinyin keep
crashing. You have to restart from applet and after a while , it crashed again.

Version-Release number of selected component (if applicable):

ibus-libs-1.2.0.20091204-2.fc12.i686
ibus-gtk-1.2.0.20091204-2.fc12.i686
ibus-pinyin-1.2.0.20090915-1.fc12.noarch
ibus-1.2.0.20091204-2.fc12.i686

How reproducible:

Do some CPU consuming work, and input characters using ibus-pinyin.


Steps to Reproduce:
1. Do some CPU consuming work
2. input something using ibus-pinyin
3. BOOM!!!

Actual results:

it crash again and again. input panel disappear and can't using ctrl-space
shortcut to call out pinyin input method again.

Expected results:

nothing special happened

Additional info:

After crash, the daemon complained: 

(ibus-daemon:29976): IBUS-WARNING **: org.freedesktop.DBus.Error.NoReply: Did
not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.

--- Additional comment from phuang at redhat.com on 2010-01-20 03:45:54 EST ---

Please try new ibus.
http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0385

--- Additional comment from phuang at redhat.com on 2010-04-07 22:41:06 EDT ---

Fixed in ibus-pinyin-1.3.1-1.fc12

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the i18n-bugs mailing list