pidgin crashed with SIGSEGV in purple_account_get_protocol_id()

Bug #682929 reported by Chow Loong Jin
98
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

Pidgin crashed when resuming from suspend to RAM, yielding this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pidgin 1:2.7.3-1ubuntu3.2
Uname: Linux 2.6.37-rc3-hyper1 x86_64
Architecture: amd64
Date: Tue Nov 30 07:55:33 2010
ExecutablePath: /usr/bin/pidgin
ProcCmdline: pidgin
ProcEnviron:
 LANGUAGE=en_SG:en
 PATH=(custom, user)
 LANG=en_SG.utf8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fe94d899409 <purple_account_get_protocol_id+9>: mov 0x30(%rdi),%rax
 PC (0x7fe94d899409) ok
 source "0x30(%rdi)" (0x260000035a) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 purple_account_get_protocol_id (account=0x260000032a) at /build/buildd/pidgin-2.7.3/./libpurple/account.c:2136
 insert_cap_failure (stats=0x7fe925ab3730) at /build/buildd/pidgin-2.7.3/./pidgin/plugins/cap/cap.c:318
 max_message_difference_cb (data=0x7fe925ab3730) at /build/buildd/pidgin-2.7.3/./pidgin/plugins/cap/cap.c:337
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
Title: pidgin crashed with SIGSEGV in purple_account_get_protocol_id()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mail netdev plugdev sambashare sbuild tape vboxusers video

Revision history for this message
Chow Loong Jin (hyperair) wrote :
visibility: private → public
visibility: public → private
Revision history for this message
Chow Loong Jin (hyperair) wrote :

The stack trace is complete enough for Pidgin, so I'm removing my CoreDump.

visibility: private → public
description: updated
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #647784, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.