[Fedora-i18n-bugs] [Bug 683143] New: [abrt] ibus-pinyin-1.3.99.20110217-2.fc15: test_case_run: Process /usr/libexec/ibus-engine-pinyin was killed by signal 6 (SIGABRT)

bugzilla at redhat.com bugzilla at redhat.com
Tue Mar 8 16:44:20 UTC 2011


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

Summary: [abrt] ibus-pinyin-1.3.99.20110217-2.fc15: test_case_run: Process /usr/libexec/ibus-engine-pinyin was killed by signal 6 (SIGABRT)

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

           Summary: [abrt] ibus-pinyin-1.3.99.20110217-2.fc15:
                    test_case_run: Process /usr/libexec/ibus-engine-pinyin
                    was killed by signal 6 (SIGABRT)
           Product: Fedora
           Version: 15
          Platform: x86_64
        OS/Version: Unspecified
            Status: NEW
 Status Whiteboard: abrt_hash:ab726ebe57f1b23c28d68c697b0d00879d078130
          Severity: unspecified
          Priority: unspecified
         Component: ibus-pinyin
        AssignedTo: pwu at redhat.com
        ReportedBy: bigslowfat at gmail.com
         QAContact: extras-qa at fedoraproject.org
                CC: i18n-bugs at lists.fedoraproject.org, pwu at redhat.com,
                    shawn.p.huang at gmail.com
    Classification: Fedora


abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 9998 bytes
cmdline: /usr/libexec/ibus-engine-pinyin --ibus
component: ibus-pinyin
Attached file: coredump, 10002432 bytes
crash_function: test_case_run
executable: /usr/libexec/ibus-engine-pinyin
kernel: 2.6.38-0.rc6.git6.1.fc15.x86_64
package: ibus-pinyin-1.3.99.20110217-2.fc15
rating: 3
reason: Process /usr/libexec/ibus-engine-pinyin was killed by signal 6
(SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1299588474
uid: 500

How to reproduce
-----
Yet another crash I met with tonight. It seems to be still related to 683137.

-- 
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