pidgin crashed with SIGSEGV in purple_certificate_verify_complete()

[Tony C]

Binary package hint: pidgin

 1) Ubuntu 8.04 - the Hardy Heron - released in April 2008.
2) pidgin:
  Installed: 1:2.4.1-1ubuntu2.2
  Candidate: 1:2.4.1-1ubuntu2.2
  Version table:
 *** 1:2.4.1-1ubuntu2.2 0
        500 http://gb.archive.ubuntu.com hardy-updates/main Packages
        500 http://security.ubuntu.com hardy-security/main Packages
        100 /var/lib/dpkg/status
     1:2.4.1-1ubuntu2 0
        500 http://gb.archive.ubuntu.com hardy/main Packages
3) Pidgin to load, even if certificate unknown.
4) Certificate not recognised by Pidgin for Nexus.Passport.com.
    After rejection of certificate by user, Pidgin crashes.

Regards

Tony

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.4.1-1ubuntu2.2
ProcAttrCurrent: unconfined
ProcCmdline: pidgin
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/purple-2/ssl-nss.so
 purple_certificate_verify_complete ()
 ?? () from /usr/lib/libpurple.so.0
 ?? () from /usr/lib/libpurple.so.0
Title: pidgin crashed with SIGSEGV in purple_certificate_verify_complete()
Uname: Linux 2.6.24-21-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:?? ()
ssl_nss_verified_cb (st=PURPLE_CERTIFICATE_INVALID,
purple_certificate_verify_complete (vrq=0xe3b7a0,
x509_tls_cached_user_auth_cb (c=0x83b5e0, id=1)
x509_tls_cached_user_auth_reject_cb (c=0x83b5e0,

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Jonathan Thomas (echidnaman)]

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!