Bug 579742

Summary: [abrt] crash in ibus-1.2.1-1.fc12: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: DemetrisK <dekacy10>
Component: ibusAssignee: Peng Huang <phuang>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: i18n-bugs, phuang
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:fbfa0ca4fedf9dfca899a40efc78f12d5f7be772
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-08 03:25:14 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 DemetrisK 2010-04-06 12:58:39 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
cmdline: python /usr/share/ibus/ui/gtk/main.py
comment: nothing actually
component: ibus
executable: /usr/bin/python
kernel: 2.6.32.10-90.fc12.i686.PAE
package: ibus-1.2.1-1.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

backtrace
-----
BFD: Warning: /var/cache/abrt/ccpp-1270557753-2144/coredump is truncated: expected core file size >= 10956800, found: 425984.
Core was generated by `python /usr/share/ibus/ui/gtk/main.py'.
Program terminated with signal 6, Aborted.
#0  0x00253424 in __kernel_vsyscall ()

Thread 1 (Thread 2144):
Cannot access memory at address 0xbfaa1a1c
From        To          Syms Read   Shared Object Library
0x0079a830  0x007b1ccf  Yes (*)     /lib/ld-linux.so.2
(*): Shared library is missing debugging information.
No symbol "__abort_msg" in current context.
No symbol "__glib_assert_msg" in current context.
Comment 1 DemetrisK 2010-04-06 12:58:42 UTC 
Created attachment 404697 [details]
File: backtrace
Comment 2 Peng Huang 2010-04-08 03:25:14 UTC 
The backtrace is not very useful to analyse the crash. If you this crash happens again, please report it again.