Bug 1105146 - [abrt] corebird: _dbus_abort(): corebird killed by SIGABRT
Summary: [abrt] corebird: _dbus_abort(): corebird killed by SIGABRT
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: corebird
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ryan Lerch
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:623a3abf4528e19e7251314958f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-05 13:35 UTC by Joshua Rich
Modified: 2015-01-29 21:19 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-29 21:19:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (53.96 KB, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: cgroup (172 bytes, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: core_backtrace (30.35 KB, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: dso_list (11.91 KB, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: environ (2.55 KB, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: maps (61.58 KB, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: open_fds (15.75 KB, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: proc_pid_status (953 bytes, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details
File: var_log_messages (458 bytes, text/plain)
2014-06-05 13:35 UTC, Joshua Rich
no flags Details

Description Joshua Rich 2014-06-05 13:35:20 UTC
Description of problem:
Just scrolling through my stream and Corebird crashed.

Version-Release number of selected component:
corebird-0.7-0.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        corebird
crash_function: _dbus_abort
executable:     /usr/bin/corebird
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _dbus_abort at dbus-sysdeps.c:94
 #3 _dbus_warn_check_failed at dbus-internals.c:290
 #4 write_or_verify_typecode at dbus-marshal-recursive.c:1730
 #5 _dbus_type_writer_write_basic at dbus-marshal-recursive.c:2326
 #6 write_basic_field at dbus-marshal-header.c:317
 #7 _dbus_header_create at dbus-marshal-header.c:613
 #8 dbus_message_new_signal at dbus-message.c:1363
 #9 emit_event at event.c:469
 #10 state_event_listener at event.c:638
 #14 atk_object_notify_state_change at atkobject.c:1191

Comment 1 Joshua Rich 2014-06-05 13:35:24 UTC
Created attachment 902542 [details]
File: backtrace

Comment 2 Joshua Rich 2014-06-05 13:35:25 UTC
Created attachment 902543 [details]
File: cgroup

Comment 3 Joshua Rich 2014-06-05 13:35:27 UTC
Created attachment 902544 [details]
File: core_backtrace

Comment 4 Joshua Rich 2014-06-05 13:35:28 UTC
Created attachment 902545 [details]
File: dso_list

Comment 5 Joshua Rich 2014-06-05 13:35:29 UTC
Created attachment 902546 [details]
File: environ

Comment 6 Joshua Rich 2014-06-05 13:35:30 UTC
Created attachment 902547 [details]
File: limits

Comment 7 Joshua Rich 2014-06-05 13:35:32 UTC
Created attachment 902548 [details]
File: maps

Comment 8 Joshua Rich 2014-06-05 13:35:33 UTC
Created attachment 902549 [details]
File: open_fds

Comment 9 Joshua Rich 2014-06-05 13:35:34 UTC
Created attachment 902550 [details]
File: proc_pid_status

Comment 10 Joshua Rich 2014-06-05 13:35:35 UTC
Created attachment 902551 [details]
File: var_log_messages

Comment 11 Ryan Lerch 2015-01-29 21:19:08 UTC
An updated version of corebird is now available in Fedora 21. Please update to that version, and refile this bug against that version if you hit this issue again.

Note also, that this issue has only been encountered once:
https://retrace.fedoraproject.org/faf/reports/383113/

So it is likely that an update to f21 and the newer version of Corebird should resolve this issue.


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