Receiving a video chat invite from Google Talk crashes Pidgin.

[Adam Buchbinder]

I have a video camera properly set up, and I can attempt to initiate a chat with a GTalk user (i.e., someone using the GMail website and Google's plugin), but if they try to initiate a chat with me, Pidgin crashes immediately.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pidgin 1:2.7.3-1ubuntu3.2
ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
Architecture: amd64
CheckboxSubmission: e8aeaf9845af0062f5473c26a064d5c6
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
Date: Wed Jul 27 12:40:49 2011
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: pidgin
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7fdeaf52e764 <jingle_transport_parse+68>: mov 0x98(%rax),%rax
 PC (0x7fdeaf52e764) ok
 source "0x98(%rax)" (0x00000098) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 jingle_transport_parse () from /usr/lib/purple-2/libjabber.so.0
 ?? () from /usr/lib/purple-2/libjabber.so.0
 ?? () from /usr/lib/purple-2/libjabber.so.0
 ?? () from /usr/lib/purple-2/libjabber.so.0
 jabber_process_packet () from /usr/lib/purple-2/libjabber.so.0
Title: pidgin crashed with SIGSEGV in jingle_transport_parse()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Adam Buchbinder (adam-buchbinder)]

I think the crash may be due to an unrecognized Jingle type. There's a patch here:

http://pidgin.im/pipermail/commits/2011-January/018747.html

and I'll link the upstream ticket.

[Apport retracing service (apport)]

StacktraceTop:
 jingle_transport_parse (transport=0x19dd080)
 jingle_content_parse_internal (content=0xfa2950)
 jingle_rtp_parse_internal (rtp=0x19dd080)
 jingle_handle_session_initiate (session=0x1a384c0,
 jabber_process_packet (js=0x1259ac0,

[Adam Buchbinder (adam-buchbinder)]

I have a fixed version in my PPA; the patch at the link seems to fix it for me, at least. It's fixed in upstream 2.7.11, according to the changelog there. (I can't receive calls from GTalk, but I can make them to GTalk, and I can see them, though they can't see me. Probably another, separate issue there.)

[Anand Kumria (wildfire)]

This fix should also be done for the packages in Ubuntu LTS too (How do I mark a bug as such in Launchpad?)

[Adam Buchbinder (adam-buchbinder)]

The process for stable release updates is here:

https://wiki.ubuntu.com/StableReleaseUpdates

But you can't nominate a patch for SRU'ing any more without being a "bug supervisor" (which I'm not); see here:

https://answers.launchpad.net/launchpad/+question/140509

So, I guess someone needs to go on the IRC channel and ask someone? The process seems to have gotten less automated since I was last involved.

[Anand Kumria (wildfire)]

I've asked on IRC, and was told it was OK to subscribe the stable-sru team.

I was also told that https://wiki.ubuntu.com/StableReleaseUpdates is geared towards the people uploading a fix (i.e. developers and not bug reporters)

So, it isn't clear to me what other things I should do apart from subscribing the relevant team.

Cheers,
Anand

[Rolf Leggewie (r0lf)]

This is fixed in the latest development release. Closing the Ubuntu task and opening a lucid task.

[Rolf Leggewie (r0lf)]

I suppose the relevant patches from upstream is http://developer.pidgin.im/viewmtn/revision/info/93f493d9c4d925a042e4b9d0211388ad38c9b92c There's a second patch mentioned in the upstream ticket but that's only to give proper credit which we may or may not want to backport as well.

[Brian Murray (brian-murray)]

Thanks for including a debdiff in this bug report and I'm sorry we didn't get to reviewing it earlier. To follow the Stable Release Updates process this bug would need to have some addiitonal information in it regarding the Impart of the bug, a test case and the regression potential of including the fix.

However, given that the next LTS of Ubuntu is out, 12.04, and the low number of people affected by the bug I'm not certain it is really worth including this fix in Lucid. Subsequently, I am setting the bug to Won't Fix and unsubscribing the sponsors team.

If you feel it is worth fixing please reopen the bug and update the description with the information required for the Stable Release Updates process. http://wiki.ubuntu.com/StableReleaseUpdates. Thanks in advance!