pidgin crashed with SIGSEGV in set_current_error()

Bug #982015 reported by Frank Baumeister on 2012-04-15
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Medium
Unassigned

Bug Description

none

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pidgin 1:2.10.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Sun Apr 15 03:19:10 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2b93f5ef25: mov (%rax),%rbx
 PC (0x7f2b93f5ef25) ok
 source "(%rax)" (0x31223d6e00002690) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/libpurple.so.0
 ?? () from /usr/lib/libpurple.so.0
 purple_signal_emit_vargs () from /usr/lib/libpurple.so.0
 purple_signal_emit () from /usr/lib/libpurple.so.0
 purple_connection_error_reason () from /usr/lib/libpurple.so.0
Title: pidgin crashed with SIGSEGV in purple_signal_emit_vargs()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Frank Baumeister (baumeisterf) wrote :
visibility: private → public

StacktraceTop:
 set_current_error (account=0x7f2b9892e9a0, new_err=0x7f2b98892b10) at /build/buildd/pidgin-2.10.3/./libpurple/account.c:2813
 connection_error_cb (gc=<optimized out>, type=PURPLE_CONNECTION_ERROR_NETWORK_ERROR, description=0x7f2b7501b876 "\nSkype not responding", unused=<optimized out>) at /build/buildd/pidgin-2.10.3/./libpurple/account.c:2851
 purple_signal_emit_vargs (instance=<optimized out>, signal=0x7f2b93ff0659 "connection-error", args=0x7fff89805c38) at /build/buildd/pidgin-2.10.3/./libpurple/signals.c:482
 purple_signal_emit (instance=<optimized out>, signal=<optimized out>) at /build/buildd/pidgin-2.10.3/./libpurple/signals.c:434
 purple_connection_error_reason (gc=0x7f2b9905dc00, reason=PURPLE_CONNECTION_ERROR_NETWORK_ERROR, description=0x7f2b7501b876 "\nSkype not responding") at /build/buildd/pidgin-2.10.3/./libpurple/connection.c:589

Changed in pidgin (Ubuntu):
importance: Undecided → Medium
summary: - pidgin crashed with SIGSEGV in purple_signal_emit_vargs()
+ pidgin crashed with SIGSEGV in set_current_error()
tags: removed: need-amd64-retrace
tags: added: running-unity
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pidgin (Ubuntu):
status: New → Confirmed
John Leach (johnleach) wrote :

Happens every time I quite Pidgin (never any other time).

tags: added: raring
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