Bug 579742 - [abrt] crash in ibus-1.2.1-1.fc12: Process /usr/bin/python was killed by signal 6 (SIGABRT)
[abrt] crash in ibus-1.2.1-1.fc12: Process /usr/bin/python was killed by sign...
Product: Fedora
Classification: Fedora
Component: ibus (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Peng Huang
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-06 08:58 EDT by DemetrisK
Modified: 2010-04-07 23:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-07 23:25:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (600 bytes, text/plain)
2010-04-06 08:58 EDT, DemetrisK
no flags Details

  None (edit)
Description DemetrisK 2010-04-06 08:58:39 EDT
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
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)

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 08:58:42 EDT
Created attachment 404697 [details]
File: backtrace
Comment 2 Peng Huang 2010-04-07 23:25:14 EDT
The backtrace is not very useful to analyse the crash. If you this crash happens again, please report it again.

Note You need to log in before you can comment on or make changes to this bug.