[Bug 817119] [NEW] Receiving a video chat invite from Google Talk crashes Pidgin.

Launchpad Bug Tracker 817119 at bugs.launchpad.net
Mon Nov 7 16:46:16 UTC 2011


You have been subscribed to a public bug by Rolf Leggewie (r0lf):

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

** Affects: pidgin
     Importance: Unknown
         Status: Fix Released

** Affects: pidgin (Ubuntu)
     Importance: Medium
         Status: Fix Released


** Tags: amd64 apport-crash maverick
-- 
Receiving a video chat invite from Google Talk crashes Pidgin.
https://bugs.launchpad.net/bugs/817119
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list