pidgin crashed with SIGSEGV in purple_connection_error()

Bug #362645 reported by David Dean
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

pidgin crashed while the computer was left running overnight

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.5-1ubuntu8
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 purple_connection_error () from /usr/lib/libpurple.so.0
 ?? () from /usr/lib/purple-2/libtwitter.so
 ?? () from /usr/lib/purple-2/ssl-nss.so
 ?? ()
 g_io_unix_dispatch (source=0x1, callback=0x90dd4d8,
Title: pidgin crashed with SIGSEGV in purple_connection_error()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

Revision history for this message
David Dean (ddean-ieee) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:purple_connection_error (gc=0x3, text=0xb77983d2 "SSL Handshake Failed")
?? ()
ssl_nss_handshake_cb (data=0x9cca920, fd=16, cond=3)
pidgin_io_invoke (source=0x9e385e8,
g_io_unix_dispatch (source=0x9e6cf48,

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
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in pidgin (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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".

Changed in pidgin (Ubuntu):
status: Incomplete → Invalid
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.