pidgin crashed with SIGSEGV in purple_account_get_ui_bool()

Bug #648669 reported by Alexcr
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

pidgin crashed with SIGSEGV in purple_account_get_ui_bool()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pidgin 1:2.7.3-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Sep 27 13:36:49 2010
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: pidgin
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x55a786 <purple_account_get_ui_bool+54>: mov 0x28(%eax),%eax
 PC (0x0055a786) ok
 source "0x28(%eax)" (0x00000029) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 purple_account_get_ui_bool () from /usr/lib/libpurple.so.0
 purple_account_get_enabled () from /usr/lib/libpurple.so.0
 purple_account_set_enabled () from /usr/lib/libpurple.so.0
 purple_connection_error_reason () from /usr/lib/libpurple.so.0
 purple_connection_error () from /usr/lib/libpurple.so.0
Title: pidgin crashed with SIGSEGV in purple_account_get_ui_bool()
UserGroups: adm admin asterisk audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev root sambashare tape video

Revision history for this message
Alexcr (alexcr-telecom) wrote :
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pidgin (Ubuntu) because there has been no activity for 60 days.]

Changed in pidgin (Ubuntu):
status: Incomplete → Expired
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.