Bug 1032295

Summary: [abrt] pidgin-2.10.7-3.fc19: sighandler: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: long
Component: farstreamAssignee: Dan Mashal <dan.mashal>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, debarshir, gholms, itamar, jsynacek, mike, mikhail.v.gavrilov, redhat2, stu, two.oes, uraeus, zioalex
Target Milestone: ---Flags: mike: needinfo? (dan.mashal)
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d31c087c496f86264d648e9e7a4364cb0bf446cc
Whiteboard: abrt_hash:84dbbc72702551c723a8f5670e1da7ae1a605398
Fixed In Version: farstream-0.1.2-10.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-13 17:22:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
farstream patch try 1 none

Description long 2013-11-19 22:56:33 UTC
Description of problem:
I have no idea how this happened.  I wasn't even actively using it at the time.

Version-Release number of selected component:
pidgin-2.10.7-3.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        pidgin --session 101681b6105f8000138057461400000020540055 --display :0
crash_function: sighandler
executable:     /usr/bin/pidgin
kernel:         3.11.7-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 sighandler
 #4 _send_src_pad_blocked_callback at /usr/lib64/gstreamer-0.10/libfsrtpconference.so
 #5 handle_pad_block at /lib64/libgstreamer-0.10.so.0
 #6 gst_pad_alloc_buffer_full at /lib64/libgstreamer-0.10.so.0
 #7 gst_tee_buffer_alloc at /usr/lib64/gstreamer-0.10/libgstcoreelements.so
 #8 gst_pad_alloc_buffer_full at /lib64/libgstreamer-0.10.so.0
 #9 gst_proxy_pad_bufferalloc_default at /lib64/libgstreamer-0.10.so.0
 #10 gst_pad_alloc_buffer_full at /lib64/libgstreamer-0.10.so.0
 #11 gst_valve_buffer_alloc at /usr/lib64/gstreamer-0.10/libgstcoreelements.so
 #12 gst_pad_alloc_buffer_full at /lib64/libgstreamer-0.10.so.0

Comment 1 long 2013-11-19 22:56:41 UTC
Created attachment 826343 [details]
File: backtrace

Comment 2 long 2013-11-19 22:56:44 UTC
Created attachment 826344 [details]
File: cgroup

Comment 3 long 2013-11-19 22:56:46 UTC
Created attachment 826345 [details]
File: core_backtrace

Comment 4 long 2013-11-19 22:56:49 UTC
Created attachment 826346 [details]
File: dso_list

Comment 5 long 2013-11-19 22:56:52 UTC
Created attachment 826347 [details]
File: environ

Comment 6 long 2013-11-19 22:56:55 UTC
Created attachment 826348 [details]
File: limits

Comment 7 long 2013-11-19 22:56:59 UTC
Created attachment 826349 [details]
File: maps

Comment 8 long 2013-11-19 22:57:01 UTC
Created attachment 826350 [details]
File: open_fds

Comment 9 long 2013-11-19 22:57:04 UTC
Created attachment 826351 [details]
File: proc_pid_status

Comment 10 long 2013-11-19 22:57:07 UTC
Created attachment 826352 [details]
File: var_log_messages

Comment 11 Egon Kastelijn 2013-12-21 13:15:29 UTC
In my case the Pidgin crash occurred when I tried to accept a SIPE audio call from a Windows Lync 2013 client.

I registered this bug for it:
https://sourceforge.net/p/sipe/bugs/230/
Which turns out to be a duplicate of:
https://sourceforge.net/p/sipe/bugs/217/
Which in refers to:
https://sourceforge.net/p/sipe/discussion/688534/thread/465db4ab/

This suggests that the problem is related to "farstream".

Comment 12 long 2013-12-23 15:21:56 UTC
I suspect my crash would also be related to Lync 2013 as we just started using it around here.

Comment 13 Egon Kastelijn 2013-12-25 19:12:50 UTC
I registered a bug for this with the Pidgin SIPE plugin maintainers.
http://sourceforge.net/p/sipe/bugs/230/ 
After looking at the backtrace the conclusion is that no code paths inside SIPE are involved in the crash, just gstreamer & farstream.

Comment 14 Fedora Admin XMLRPC Client 2014-02-17 13:01:41 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 15 Fedora Admin XMLRPC Client 2014-02-17 13:03:18 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 16 Michael Cronenworth 2014-07-30 19:29:39 UTC
*** Bug 1124989 has been marked as a duplicate of this bug. ***

Comment 17 Michael Cronenworth 2014-08-08 17:14:35 UTC
Created attachment 925254 [details]
farstream patch try 1

So I caught this in gdb and found the problem easily enough.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f13d139a700 (LWP 30767)]
0x00007f13ebdd5115 in _send_src_pad_blocked_callback (pad=0x2611c60, 
    blocked=<optimized out>, user_data=<optimized out>)
    at fs-rtp-session.c:3864
3864	        error->message);
(gdb) p error
$1 = (GError *) 0x0

Farstream is clearing the error pointer and then not re-initializing it. I noticed 3 possible areas where the error pointer should have been re-initialized. The attached patch appears to fix this issue. Instead of crashing I get a "A non-recoverable Farstream error has occurred." message.

Comment 18 Oren Oichman 2014-08-20 09:17:22 UTC
Another user experienced a similar problem:

when getting a call over lync, before I had a chance to answer the call
the application crashed

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        pidgin
crash_function: sighandler
executable:     /usr/bin/pidgin
kernel:         3.15.10-200.fc20.x86_64
package:        pidgin-2.10.9-1.fc20
reason:         pidgin killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 19 Michael Cronenworth 2014-08-20 22:32:41 UTC
@Dan, could you apply my patch?

Comment 20 Michael Cronenworth 2014-09-04 15:22:54 UTC
*** Bug 1028784 has been marked as a duplicate of this bug. ***

Comment 21 Alessandro Surace 2014-12-09 14:54:31 UTC
Guys any update to this bug?

Comment 22 Oren Oichman 2015-02-23 11:59:11 UTC
Another user experienced a similar problem:

trying to answer a SIP call

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        pidgin --session 205e8dcdb-957b-46e2-90e6-fbc4e732e523 --display :0.0
crash_function: sighandler
executable:     /usr/bin/pidgin
kernel:         3.18.7-100.fc20.x86_64
package:        pidgin-2.10.10-3.fc20
reason:         pidgin killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 23 Fedora Update System 2015-03-06 22:31:39 UTC
farstream-0.1.2-10.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/farstream-0.1.2-10.fc22

Comment 24 Fedora Update System 2015-03-06 22:32:23 UTC
farstream-0.1.2-10.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/farstream-0.1.2-10.fc21

Comment 25 Fedora Update System 2015-03-06 22:33:33 UTC
farstream-0.1.2-10.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/farstream-0.1.2-10.fc20

Comment 26 Fedora Update System 2015-03-09 08:24:40 UTC
Package farstream-0.1.2-10.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing farstream-0.1.2-10.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3405/farstream-0.1.2-10.fc22
then log in and leave karma (feedback).

Comment 27 Fedora Update System 2015-03-13 17:22:45 UTC
farstream-0.1.2-10.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 28 Fedora Update System 2015-03-23 07:08:27 UTC
farstream-0.1.2-10.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 29 Fedora Update System 2015-03-23 07:10:26 UTC
farstream-0.1.2-10.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.