pidgin crashed with SIGSEGV in g_idle_dispatch()

Bug #1221318 reported by Simon THOBY
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was trying to connect pidging to lync using the sipe plugin when it crashed.The windows closed and it indicate in the console : "core dumped".

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: pidgin 1:2.10.7-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
Date: Thu Sep 5 18:12:43 2013
Disassembly: => 0xb5dc7820: Cannot access memory at address 0xb5dc7820
ExecutablePath: /usr/bin/pidgin
InstallationDate: Installed on 2013-08-05 (31 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130804)
MarkForUpload: True
ProcCmdline: pidgin
SegvAnalysis:
 Segfault happened at: 0xb5dc7820: Cannot access memory at address 0xb5dc7820
 PC (0xb5dc7820) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 g_idle_dispatch (source=source@entry=0xb808afc8, callback=0xb5dc7820, user_data=0xb8013d78) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:5250
 g_main_dispatch (context=0xb7904538, context@entry=0xb79c0ca0) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3065
 g_main_context_dispatch (context=context@entry=0xb7904538) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3641
 g_main_context_iterate (context=0xb7904538, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3712
Title: pidgin crashed with SIGSEGV in g_idle_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp

Revision history for this message
Simon THOBY (simonthoby-deactivatedaccount) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_idle_dispatch (source=source@entry=0xb808afc8, callback=0xb5dc7820, user_data=0xb8013d78) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:5250
 g_main_dispatch (context=0xb7904538) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3065
 g_main_context_dispatch (context=context@entry=0xb7904538) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3641
 g_main_context_iterate (context=0xb7904538, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3712

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-i386-retrace
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.