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
Created attachment 826343 [details] File: backtrace
Created attachment 826344 [details] File: cgroup
Created attachment 826345 [details] File: core_backtrace
Created attachment 826346 [details] File: dso_list
Created attachment 826347 [details] File: environ
Created attachment 826348 [details] File: limits
Created attachment 826349 [details] File: maps
Created attachment 826350 [details] File: open_fds
Created attachment 826351 [details] File: proc_pid_status
Created attachment 826352 [details] File: var_log_messages
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".
I suspect my crash would also be related to Lync 2013 as we just started using it around here.
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.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 1124989 has been marked as a duplicate of this bug. ***
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.
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
@Dan, could you apply my patch?
*** Bug 1028784 has been marked as a duplicate of this bug. ***
Guys any update to this bug?
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
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
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
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
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).
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.
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.
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days