Red Hat Bugzilla – Bug 882681
[abrt] empathy-3.6.2-1.fc18: _dbus_list_unlink: Process /usr/libexec/empathy-chat was killed by signal 11 (SIGSEGV)
Last modified: 2014-02-05 17:54:04 EST
Version-Release number of selected component:
Thread no. 1 (10 frames)
#0 _dbus_list_unlink at dbus-list.c:499
#1 _dbus_list_pop_first_link at dbus-list.c:625
#2 _dbus_message_loader_pop_message_link at dbus-message.c:4316
#3 _dbus_transport_queue_messages at dbus-transport.c:1133
#4 do_reading at dbus-transport-socket.c:851
#6 socket_handle_watch at dbus-transport-socket.c:932
#7 _dbus_transport_handle_watch at dbus-transport.c:885
#8 _dbus_connection_handle_watch at dbus-connection.c:1515
#9 dbus_watch_handle at dbus-watch.c:700
#10 io_handler_dispatch at dbus-gmain.c:221
Created attachment 656113 [details]
Created attachment 656114 [details]
Created attachment 656115 [details]
Created attachment 656116 [details]
Created attachment 656117 [details]
Created attachment 656118 [details]
Created attachment 656119 [details]
Created attachment 656120 [details]
Created attachment 656121 [details]
Created attachment 656122 [details]
Created attachment 656123 [details]
*** Bug 877674 has been marked as a duplicate of this bug. ***
*** Bug 883587 has been marked as a duplicate of this bug. ***
*** Bug 865295 has been marked as a duplicate of this bug. ***
Are you still seeing this bug with empathy-3.6.3-1?
Tried to open second conversation in Empathy - it couldn't handle tabs.
OS Release: Fedora release 18 (Spherical Cow)
Thread 1 (Thread 0x7fd78861e9c0 (LWP 16891)):
#0 0x0000003375227ed7 in _dbus_list_unlink (list=list@entry=0x1877380, link=link@entry=0x1876e68) at dbus-list.c:499
A crash here is often a symptom of threading not having been initialized. I wonder whether another thread has touched libdbus without anyone calling dbus_threads_init_default()?
The threads are:
* 9: GDBus. OK.
* 8: PulseAudio. Does this use libdbus?
* 7: telepathy-logger. Does this use libdbus in non-main threads?
* 6: d-conf. OK.
* 5: Evolution source registry. Does this use libdbus in non-main threads?
* 1: main thread
The current state-of-the-art in making libdbus thread-safe is to call dbus_threads_init_default() from the main thread before you do anything else, preferably early in main(). Yes I know that's a design flaw; it's one we've had for years.
I have a patch-set to make libdbus thread-safe by default, which is clearly the correct long-term solution (but was quite a subtle thing to achieve). Reviewers extremely welcome, especially if they are D-Bus committers (e.g. Colin Walters, David Zeuthen, Lennart Poettering); but criticisms or "I am not a maintainer but it looks good to me" from any experienced developer are very welcome. See <https://bugs.freedesktop.org/show_bug.cgi?id=54972>.
To attempt a short-term fix, please try inserting
if (!dbus_threads_init_default ())
g_error ("fatal error: not enough memory to initialize threads");
near the beginning of Empathy's main(). You will need to depend on libdbus (dbus-1) if you don't already.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.