After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 735993 - Lync calls crash Pidgin using SIPE plugin
Lync calls crash Pidgin using SIPE plugin
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
1.4.1
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-03 20:45 UTC by Daniel
Modified: 2016-02-21 23:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel 2014-09-03 20:45:28 UTC
Some details from previous bug 724244:
{
The Pidgin SIPE plugin to connect to Microsoft Lync servers will crash if a
phone call is attempted. The backtrace seems to indicate an issue in
gst-plugins-ugly. You may find backtraces in the fd.o or sf.net bugs.

See these bug reports for more information:
http://sourceforge.net/p/sipe/bugs/217/
https://bugs.freedesktop.org/show_bug.cgi?id=71253
https://bugzilla.redhat.com/show_bug.cgi?id=1028784
}

My personal observation is that pidgin will crash only if somebody tries to call me directly (an incomming call). But once I call somebody, it doesn't crash, works fine.
The problem is present still from older versions even up to the current stable 1.4.1 one.

As can be seen on one of the provided URL: https://bugs.freedesktop.org/show_bug.cgi?id=71253 , the farstream developers already pointed with finger to gstreamer to be the responsible for these crashes.
But Michael Cronenworth in the previous bug 724244 said he made some own tracing of the problem back to the farstream again, and he made some patch "https://bugzilla.redhat.com/attachment.cgi?id=925254" for older version of farstream 0.1.2.
Therefore it is still unclear which of those two - gstreamer or farstream - is truly responsible for the crash.

Regarding providing you further debugging details (Full debugging symbols for all involved libraries would be good. Perhaps also run pidgin in valgrind to see if it picks up anything.), I'm affraid I can't as I'm not that skilled with debugging, but I'll try ask that Michael, which looks like a skilled "probably" developer.
Comment 1 Michael Cronenworth 2014-09-04 15:35:32 UTC
Please note that I was debugging voice calls and not video calls. The Fd.o bug is for video calls. The Red Hat bug is a duplicate and I just closed it.

Voice calls were failing (w/ farstream 0.1.2) at this point:
https://bugzilla.redhat.com/show_bug.cgi?id=1032295#c17
Comment 2 Tim-Philipp Müller 2014-09-04 18:45:42 UTC
I would like to see a stack trace with full debugging symbols involving GStreamer 1.4 and/or a valgrind log with the same.
Comment 3 Daniel 2014-09-04 20:18:26 UTC
(In reply to comment #1)
> Please note that I was debugging voice calls and not video calls. The Fd.o bug
> is for video calls. The Red Hat bug is a duplicate and I just closed it.
> 
> Voice calls were failing (w/ farstream 0.1.2) at this point:
> https://bugzilla.redhat.com/show_bug.cgi?id=1032295#c17


I was also talking about voice calls, of course.
Comment 4 Michael Cronenworth 2014-09-04 20:31:17 UTC
I purposely left myself off the CC list due to lack of time to debug this. I only spent the time to debug the current version of Pidgin because I couldn't work with Pidgin crashing any longer. Unless Pidgin would consider accepting my work to compile with gstreamer 1 I, as Tim-Philipp feels, don't see a need to pursue this.
Comment 5 Tim-Philipp Müller 2016-02-21 23:33:49 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!