Red Hat Bugzilla – Bug 1009325
[abrt] empathy-3.6.4-3.fc18: debug_codec_cap: Process /usr/libexec/empathy-call was killed by signal 6 (SIGABRT)
Last modified: 2014-02-05 17:24:09 EST
Description of problem:
Trying to initiate or answer a video or voice call via XMPP always results in this crash.
Version-Release number of selected component:
runlevel: N 5
var_log_messages: Sep 18 00:22:18 vaioz abrt: Saved core dump of pid 23225 (/usr/libexec/empathy-call) to /var/tmp/abrt/ccpp-2013-09-18-00:22:18-23225 (74162176 bytes)
Thread no. 1 (10 frames)
#4 debug_codec_cap at fs-rtp-discover-codecs.c:127
#5 debug_codec_cap_list at fs-rtp-discover-codecs.c:143
#6 detect_recv_codecs at fs-rtp-discover-codecs.c:844
#7 fs_rtp_blueprints_get at fs-rtp-discover-codecs.c:264
#8 fs_rtp_session_constructed at fs-rtp-session.c:1032
#10 g_object_new_valist at gobject.c:1835
#12 fs_rtp_session_new at fs-rtp-session.c:2114
#13 fs_rtp_conference_new_session at fs-rtp-conference.c:524
#14 fs_conference_new_session at fs-conference.c:141
#15 got_content_media_properties at call-content.c:1154
Created attachment 799197 [details]
Created attachment 799198 [details]
Created attachment 799199 [details]
Created attachment 799200 [details]
Created attachment 799201 [details]
Created attachment 799202 [details]
Created attachment 799203 [details]
Created attachment 799205 [details]
Created attachment 799206 [details]
I tried to accept an incoming video call from google, and then it died
reason: Process /usr/libexec/empathy-call was killed by signal 6 (SIGABRT)
runlevel: N 5
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.