Bug 566871

Summary: [abrt] crash in ibus-1.2.0.20100111-2.fc12
Product: [Fedora] Fedora Reporter: Mark Richards <mark.richards>
Component: gtk2Assignee: Matthias Clasen <mclasen>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: i18n-bugs, mclasen, pnemade, yshao
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:97bc69bce01cda40ec5cfbc31ed4a16766f23bc9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-03 05:32:07 UTC Type: ---
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
File: backtrace none

Description Mark Richards 2010-02-20 04:29:41 UTC 
abrt 1.0.6 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/ibus/ui/gtk/main.py
component: ibus
executable: /usr/bin/python
kernel: 2.6.31.12-174.2.3.fc12.x86_64
package: ibus-1.2.0.20100111-2.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
Comment 1 Mark Richards 2010-02-20 04:29:43 UTC 
Created attachment 395213 [details]
File: backtrace
Comment 2 Peng Huang 2010-02-20 05:08:58 UTC 
I think it is gtk bug.
Comment 3 Parag Nemade 2010-09-02 09:40:27 UTC 
Please provide steps to reproduce this crash otherwise I see ibus is working fine for me. Also ibus is now updated to 1.3.6 in F12
Comment 4 Mark Richards 2010-09-02 12:25:57 UTC 
Sorry, I don't know how to reproduce it.  This crash just occurred while I was using my workstation normally.
Comment 5 Parag Nemade 2010-09-03 05:32:07 UTC 
Thanks. I will close this now. If you will see any issues with ibus again please report bug against ibus.