pidgin crashed with SIGSEGV in add_room_to_blist_cb()

Bug #976481 reported by Guillaume Romagny
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Pidgin crashes when using Google Talk features (XMPP)

before I have this message on the shell screen
(Pidgin:7858): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pidgin 1:2.10.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Sun Apr 8 11:56:17 2012
ExecutablePath: /usr/bin/pidgin
ProcCmdline: pidgin
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
Title: pidgin crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Guillaume Romagny (golfromeo.ovh) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in pidgin (Ubuntu):
importance: Undecided → Medium
summary: - pidgin crashed with SIGSEGV in g_signal_emit_valist()
+ pidgin crashed with SIGSEGV in add_room_to_blist_cb()
tags: removed: need-amd64-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
Revision history for this message
arsenix (arsenix) wrote :

I also have this issue since upgrading to Ubuntu 12.10. Pidgin crashes after a few minutes of being signed into google talk. Could be tied to users signing on/off or some other type of event, but all functions seem to work (receiving and sending messages etc).

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.