pidgin crashed with SIGSEGV in g_main_context_dispatch()

Bug #274441 reported by Uphaar Agrawalla
140
This bug affects 15 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

Pidgin crashed when trying to login.

ProblemType: Crash
Architecture: amd64
Date: Thu Sep 25 20:57:11 2008
Disassembly: 0x0:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.4.1-1ubuntu2.1
PackageArchitecture: amd64
ProcCmdline: pidgin
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 ?? ()
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.24-21-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mldonkey netdev plugdev powerdev scanner video

Revision history for this message
Uphaar Agrawalla (uphaar) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
headline_click_callback (data=0xfe40c0) at ../../pidgin/gtkblist.c:4437
IA__g_main_context_dispatch (context=0x722280) at /build/buildd/glib2.0-2.16.4/glib/gmain.c:2012
g_main_context_iterate (context=0x722280, block=1, dispatch=1, self=<value optimized out>)
IA__g_main_loop_run (loop=0xeda0c0) at /build/buildd/glib2.0-2.16.4/glib/gmain.c:2853

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Magnus S (magnuss) wrote :

Hi, thanks for the report and the attached files. Are you still able to reproduce this bug? If so, please attach a fresh backtrace (https://wiki.ubuntu.com/Backtrace) to this report.

Thanks!
//magnus

Changed in pidgin:
status: New → Confirmed
Revision history for this message
geert (blaat-euronet) wrote :

I did not encounter the bug again.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

This bug appears to be happening to people in jaunty alpha 5. A quick search found 4 identically named bugs likely all started by apport. Should they get marked as duplicates of eachother?

#212795 #274441 #335998 #324325

Revision history for this message
Andrea Caminiti (nrayever) wrote :

happened to some hours ago. and it happened when i unplugged my 3g phone and wireless connection was being established.

regards

nrayever

Revision history for this message
Andrea Caminiti (nrayever) wrote :

Is there any solution for this bug? Because just happened to me again. I have to support Elias theory. I installed from ubuntu 9.04 alpha 5

Regards.

nrayever

Revision history for this message
Bruno Martins (skorzen) wrote :

Well, I think pidgin is becoming highly unstable. Until some 'important' (at least, to me) updates come out, I will be using emesene.

Revision history for this message
Alejandro Vidal (mancvso) wrote :

confirmed on jaunty beta

Revision history for this message
Casey Jones (alpergurel) wrote :

I still have it

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Casey, what release are you running? Please do "apport-collect 274441". Thank you.

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.