pidgin crashed with SIGSEGV in purple_account_get_protocol_id()

Bug #647784 reported by John Dundas on 2010-09-25
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)

Bug Description

Binary package hint: pidgin


ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pidgin 1:2.7.3-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Sat Sep 25 23:15:51 2010
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: pidgin
 PATH=(custom, user)
 Segfault happened at: 0x7f6cbee13409 <purple_account_get_protocol_id+9>: mov 0x30(%rdi),%rax
 PC (0x7f6cbee13409) ok
 source "0x30(%rdi)" (0xec0000012c) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pidgin
 purple_account_get_protocol_id () from /usr/lib/
 ?? () from /usr/lib/pidgin/
 ?? () from /usr/lib/pidgin/
 ?? () from /lib/
 g_main_context_dispatch () from /lib/
Title: pidgin crashed with SIGSEGV in purple_account_get_protocol_id()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

John Dundas (johndundass) wrote :

 purple_account_get_protocol_id (account=0xec000000fc)
 insert_cap_failure (stats=0x15e0000)
 max_message_difference_cb (data=0x15e0000)
 g_timeout_dispatch (source=0x1629c60,
 g_main_context_dispatch (context=0xd82e90)

Changed in pidgin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Charlie Kravetz (charlie-tca) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in pidgin (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers