pidgin crashed with SIGSEGV in _sasl_MD5Update()

Bug #362890 reported by Aydar Khabibullin
6
Affects Status Importance Assigned to Milestone
cyrus-sasl2 (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: pidgin

When I run pidgin, it suddenly closed.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.5-1ubuntu8
ProcCmdline: pidgin
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/libsasl2.so.2
 ?? () from /usr/lib/libsasl2.so.2
 _sasl_MD5Update () from /usr/lib/libsasl2.so.2
 ?? () from /usr/lib/sasl2/libdigestmd5.so.2
 ?? () from /usr/lib/sasl2/libdigestmd5.so.2
Title: pidgin crashed with SIGSEGV in _sasl_MD5Update()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Aydar Khabibullin (aydar-kh) wrote :
description: updated
description: updated
description: updated
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:Decode (output=0xbf92c04c, input=0x9c4cfca "", len=64)
MD5Transform (state=0xbf92c130, block=0x0) at md5.c:195
_sasl_MD5Update (context=0xbf92c130,
MD5_UTF8_8859_1 (utils=0x92693e0, ctx=0xbf92c130,
DigestCalcSecret (utils=0x92693e0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in pidgin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
affects: pidgin (Ubuntu) → cyrus-sasl2 (Ubuntu)
Revision history for this message
Chuck Short (zulcss) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in cyrus-sasl2 (Ubuntu):
importance: Medium → Low
status: New → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in cyrus-sasl2 (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
darkrain42 (darkrain42) wrote :

This ticket was closed incorrectly. It already contains a perfectly good backtrace as decoded by Apport retracing service.

FWIW, this has been reported to Pidgin upstream as http://developer.pidgin.im/ticket/11560 (Windows) and in Spectrum (open-source XMPP transport that leverages libpurple), with the same backtrace.

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.