Bug 894295

Summary: [abrt] ibus-1.4.99.20121109-9.fc17: _dbus_abort: Process /usr/libexec/ibus-ui-gtk3 was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: dongming3720 <dongming3720>
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: i18n-bugs, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:174b2229074ef599b8619e7e713a3dd7c0e5d39e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-14 06:43:06 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description dongming3720 2013-01-11 10:57:03 UTC 
Version-Release number of selected component:
ibus-1.4.99.20121109-9.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-ui-gtk3
crash_function: _dbus_abort
kernel:         3.6.11-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #2 _dbus_abort at dbus-sysdeps.c:94
: #3 _dbus_warn_check_failed at dbus-internals.c:289
: #4 dbus_message_iter_append_basic at dbus-message.c:2526
: #6 append_cache_item at cache-adaptor.c:193
: #7 emit_cache_add at cache-adaptor.c:281
: #8 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312
: #9 _g_closure_invoke_va at gclosure.c:840
: #12 add_object at ../../atk-adaptor/accessible-cache.c:199
: #13 add_pending_items at ../../atk-adaptor/accessible-cache.c:307
: #18 switcher_run at switcher.c:456
Comment 1 dongming3720 2013-01-11 10:57:06 UTC 
Created attachment 676789 [details]
File: core_backtrace
Comment 2 dongming3720 2013-01-11 10:57:08 UTC 
Created attachment 676790 [details]
File: environ
Comment 3 dongming3720 2013-01-11 10:57:10 UTC 
Created attachment 676791 [details]
File: backtrace
Comment 4 dongming3720 2013-01-11 10:57:12 UTC 
Created attachment 676792 [details]
File: limits
Comment 5 dongming3720 2013-01-11 10:57:14 UTC 
Created attachment 676793 [details]
File: cgroup
Comment 6 dongming3720 2013-01-11 10:57:16 UTC 
Created attachment 676794 [details]
File: smolt_data
Comment 7 dongming3720 2013-01-11 10:57:18 UTC 
Created attachment 676795 [details]
File: executable
Comment 8 dongming3720 2013-01-11 10:57:20 UTC 
Created attachment 676796 [details]
File: maps
Comment 9 dongming3720 2013-01-11 10:57:22 UTC 
Created attachment 676797 [details]
File: dso_list
Comment 10 dongming3720 2013-01-11 10:57:24 UTC 
Created attachment 676798 [details]
File: proc_pid_status
Comment 11 dongming3720 2013-01-11 10:57:26 UTC 
Created attachment 676799 [details]
File: var_log_messages
Comment 12 dongming3720 2013-01-11 10:57:28 UTC 
Created attachment 676800 [details]
File: open_fds
Comment 13 fujiwara 2013-01-14 12:05:39 UTC 
(In reply to comment #3)
> Created attachment 676791 [details]
> File: backtrace

(In reply to comment #0)
> truncated backtrace:
> :Thread no. 1 (10 frames)
> : #2 _dbus_abort at dbus-sysdeps.c:94
> : #3 _dbus_warn_check_failed at dbus-internals.c:289
> : #4 dbus_message_iter_append_basic at dbus-message.c:2526
> : #6 append_cache_item at cache-adaptor.c:193
> : #7 emit_cache_add at cache-adaptor.c:281
> : #8 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312
> : #9 _g_closure_invoke_va at gclosure.c:840
> : #12 add_object at ../../atk-adaptor/accessible-cache.c:199
> : #13 add_pending_items at ../../atk-adaptor/accessible-cache.c:307
> : #17 g_main_loop_run at gmain.c:3340
> : #18 switcher_run at switcher.c:456

I cannot reproduce your problem.
Are you still able to see the backtrace?
Comment 14 fujiwara 2013-06-14 06:43:06 UTC 
If you still reproduce this issue, please comment it here again.