telepathy-haze crashed with SIGSEGV in purple_account_get_password()

Bug #212662 reported by visualdeception
52
Affects Status Importance Assigned to Milestone
Pidgin
Fix Released
Medium
telepathy-haze (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: telepathy-haze

Occurred in Ubuntu 8.04. MSN portion and Jabber had both given connection error.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Apr 5 23:52:12 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/telepathy/telepathy-haze
NonfreeKernelModules: nvidia
Package: telepathy-haze 0.2.0-1
PackageArchitecture: i386
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 purple_account_get_password () from /usr/lib/libpurple.so.0
 ?? () from /usr/lib/libpurple.so.0
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: telepathy-haze crashed with SIGSEGV in purple_account_get_password()
Uname: Linux 2.6.24-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin nagios plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
visualdeception (sdudenhofer) wrote :

Binary package hint: telepathy-haze

Occurred in Ubuntu 8.04. MSN portion and Jabber had both given connection error.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Apr 5 23:52:12 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/telepathy/telepathy-haze
NonfreeKernelModules: nvidia
Package: telepathy-haze 0.2.0-1
PackageArchitecture: i386
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 purple_account_get_password () from /usr/lib/libpurple.so.0
 ?? () from /usr/lib/libpurple.so.0
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: telepathy-haze crashed with SIGSEGV in purple_account_get_password()
Uname: Linux 2.6.24-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin nagios plugdev powerdev scanner video

Revision history for this message
visualdeception (sdudenhofer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:purple_account_get_password (account=0x206e6f69)
purple_connection_disconnect_cb (data=0x206e6f69)
g_timeout_dispatch (source=0x810c700, callback=0x206e6f69,
IA__g_main_context_dispatch (context=0x80606e0)
g_main_context_iterate (context=0x80606e0, block=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in telepathy-haze:
importance: Undecided → Medium
Revision history for this message
In , Will Thompson (wjt) wrote :

As far as I can tell, libpurple removes the timeout at the right time; there's no code path that can let haze's idle callback fire before libpurple's one has either run or been cancelled. So I can't see why this would happen, and I can't reproduce it any more.

Revision history for this message
In , Will Thompson (wjt) wrote :

If you supply incorrect credentials haze crashes on connection, every time.

Shortly after

(haze:20176): tp-glib-DEBUG: tp_base_connection_change_status: was 1, now 2, for reason 3
** (haze:20176): DEBUG: haze_im_channel_factory_iface_close_all: closing im channels
(haze:20176): tp-glib-DEBUG: tp_base_connection_change_status: emitting status-changed to 2, for reason 3
** Message: [info] account: Disconnecting account 0x9261ee0
** Message: [info] connection: Disconnecting connection 0x9265588
** Message: [info] connection: Destroying connection 0x9265588

you dereference freed memory of some form, usually because the prpl is inspecting its info stored on the connection after it's destroyed.

Revision history for this message
In , Will Thompson (wjt) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is a pidgin libpurple one

Revision history for this message
Brian Curtis (bcurtiswx) wrote :

Thank you for your bug report. Do you still experience this issue with an up-to-date system?

Changed in pidgin:
status: New → Incomplete
Revision history for this message
Craig Maloney (craig-decafbad) wrote :

Yes, it appears to still occasionally crash. Worse, if it crashes, Empathy will not display any messages. I had a conversation where the other party was responding to me, but I wasn't receiving their messages at all. This is with Pidgin 2.4.3. If the work-around for AIM is to use libpurple, perhaps the integration needs to be more robust and gracefully recover from such issues.

Revision history for this message
Sunil Mohan Adapa (sunilmohan-fsf) wrote :

This and other bugs (#212662, #214478, #217842, #218816) seem to be caused because of double free from purple_account_disconnect called twice. The issue is a telepathy-haze one. The upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=14933 is fixed and released as part of 0.2.1 release.

Changed in pidgin:
status: Unknown → Fix Released
Revision history for this message
Will Thompson (wjt) wrote :

As Sunil said, this is fixed in telepathy-haze 0.2.1.

Changed in telepathy-haze:
status: Incomplete → Fix Released
Changed in pidgin:
importance: Unknown → Medium
Changed in pidgin:
importance: Medium → Unknown
Changed in pidgin:
importance: Unknown → Medium
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.