pidgin crashed with SIGSEGV in g_simple_async_result_complete()

[Rainer Rohde]

Seems as if there's no pidgin window coming up, even though pidgin seems to have started. I hear notifications of people coming online, but when clicking on the message indicator, no user-list pops up.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: pidgin 1:2.10.6-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Tue Jan 22 07:05:32 2013
Disassembly: => 0x7f38e1e838c0: Cannot access memory at address 0x7f38e1e838c0
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/pidgin
MarkForUpload: True
ProcCmdline: pidgin
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f38e1e838c0: Cannot access memory at address 0x7f38e1e838c0
 PC (0x7f38e1e838c0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: lp lpadmin sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 g_simple_async_result_complete (simple=0x7f39058fc2b0) at /build/buildd/glib2.0-2.35.4/./gio/gsimpleasyncresult.c:777
 complete_in_idle_cb (data=0x7f39058fc2b0) at /build/buildd/glib2.0-2.35.4/./gio/gsimpleasyncresult.c:789
 g_main_dispatch (context=0x7f39057e5350) at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:2784
 g_main_context_dispatch (context=context@entry=0x7f39057e5350) at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:3288

[Launchpad Janitor (janitor)]

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