Pidgin crashes silently when an audio call is incoming

for Adium, Pidgin, Miranda and Telepathy IM Framework

Brought to you by: aavelar, stefanb2

#217 Pidgin crashes silently when an audio call is incoming

Milestone: OBSOLETE_(1.17.x)

Status: closed-invalid

Owner: Jakub Adam

Labels: None

Category: Pidgin

Priority: 5

Updated: 2016-04-23

Created: 2013-10-21

Creator: cmeury

Private: No

Copied over from https://developer.pidgin.im/ticket/15784

Steps to reproduce

Run Pidgin 2.10.7-4 with libpurple 2.10.7-4 and pidgin-sipe1.17.0-1 on Arch-Linux
Get a call from a Lync 2013 user

Observation

Pidgin crashes immediately, sometimes showing the audio call dialog for a brief moment.
No crash information is displayed whatsoever, it just vanishes. See core dump in the pidgin issue (no symbols unfortunately).

Related

Discussion

cmeury - 2013-10-21

What other information, log files, versions can I provide to help with this one?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2013-10-22

FAQ

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

cmeury - 2013-10-22

Thanks Stefan, see attached the debug log.

sipe-voice-call-crash-truncated.log

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2013-10-22

assigned_to: Jakub Adam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2013-10-22

Can you please add a backtrace? I have a hunch that this is NOT a SIPE crash.

According to the log farstream is running out of valid candidates and then (I guess?) crashes. I vaguely remember seeing something similar, AFAIR something about missing codec package on your machine.

Jakub probably will know better.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2013-10-22

status: open --> closed-invalid
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2013-10-22

This forum entry shows the exact same error. The provided GDB backtrace shows no code path touching SIPE, just in farstream.

I would suggest to install farstream debugging information and provide the GDB backtrace to farstream project.

Closing as INVALID based on the provided information.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

cmeury - 2013-10-22

Thanks, Stefan - very helpful, I will try to follow up with farstream.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marat - 2014-02-07

it's funny,
farstream say -> this is not a Farstream bug.. It seems like it's a bug in the GStreamer

https://bugs.freedesktop.org/show_bug.cgi?id=71253

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.