pidgin crashed with SIGSEGV in g_source_unref_internal()

Bug #1029523 reported by Austin S. Hemmelgarn
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Don't really know what happened, occured during startup, but only the first time I started pidgin.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pidgin 1:2.10.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Thu Jul 26 11:48:02 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: pidgin
SegvAnalysis:
 Segfault happened at: 0x7fdab45aa723 <g_source_unref_internal+195>: mov 0x18(%rax),%rax
 PC (0x7fdab45aa723) ok
 source "0x18(%rax)" (0x7fdaa04250f8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 g_source_unref_internal (source=0x7fdab8c891b0, context=0x7fdab7fec040, have_lock=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:1645
 g_main_dispatch (context=0x7fdab7fec040) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2567
 g_main_context_dispatch (context=0x7fdab7fec040) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3075
 g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x7fdab7fec040, self=<optimized out>) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3146
 g_main_context_iterate (context=0x7fdab7fec040, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083
Title: pidgin crashed with SIGSEGV in g_source_unref_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm avahi backup bluetooth cdrom davfs2 dialout dip fuse games lastfm libvirtd lpadmin mlocate netdev operator plugdev pulse-access sambashare scanner ssh staff sudo users vboxusers video

Revision history for this message
Austin S. Hemmelgarn (ahferroin7) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_source_unref_internal (source=0x7fdab8c891b0, context=0x7fdab7fec040, have_lock=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:1645
 g_main_dispatch (context=0x7fdab7fec040) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:2567
 g_main_context_dispatch (context=0x7fdab7fec040) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3075
 g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x7fdab7fec040, self=<optimized out>) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3146
 g_main_context_iterate (context=0x7fdab7fec040, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in pidgin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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