Bug 585462 - [abrt] crash in ibus-1.3.2-1.fc12: Process /usr/libexec/ibus-x11 was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in ibus-1.3.2-1.fc12: Process /usr/libexec/ibus-x11 was killed b...
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peng Huang
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:9a93c2ce0f85ffac0c8441bf76b...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-24 07:46 UTC by sho.shimauchi
Modified: 2010-05-04 23:54 UTC (History)
2 users (show)

Fixed In Version: ibus-1.3.3-1.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-04 23:54:50 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (7.57 KB, text/plain)
2010-04-24 07:46 UTC, sho.shimauchi
no flags Details

Description sho.shimauchi 2010-04-24 07:46:47 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/ibus-x11 --kill-daemon
component: ibus
executable: /usr/libexec/ibus-x11
global_uuid: 9a93c2ce0f85ffac0c8441bf76b17ffa5ff7d2b0
package: ibus-1.3.2-1.fc12
rating: 4
reason: Process /usr/libexec/ibus-x11 was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
1. run IM Chooser (current IM: SCIM)
2. choose iBus
3. then crash immediately

Comment 1 sho.shimauchi 2010-04-24 07:46:49 UTC
Created attachment 408785 [details]
File: backtrace

Comment 2 Peng Huang 2010-05-02 03:36:36 UTC
Does it always happen?

Comment 3 sho.shimauchi 2010-05-02 03:45:47 UTC
No. it happend only one time, and I've never had the error since then.

Comment 4 Fedora Update System 2010-05-04 06:56:04 UTC
ibus-1.3.3-1.fc12 has been submitted as an update for Fedora 12.

Comment 5 Peng Huang 2010-05-04 06:57:07 UTC
Fixed. Thanks.

Comment 6 Fedora Update System 2010-05-04 23:54:46 UTC
ibus-1.3.3-1.fc12 has been pushed to the Fedora 12 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.