pidgin crashed with SIGSEGV in notify_get_server_caps()

[W. Scott Lockwood III]

Binary package hint: pidgin

1
Description: Ubuntu lucid (development branch)
Release: 10.04

2
pidgin:
  Installed: 1:2.6.6-1ubuntu4
  Candidate: 1:2.6.6-1ubuntu4
  Version table:
 *** 1:2.6.6-1ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
     1:2.6.6-1ubuntu3~pidgin.10.04 0
        500 http://ppa.launchpad.net/pidgin-developers/ppa/ubuntu/ lucid/main Packages

3
I expected to be able to disable notifications, and then re-enable them.

4
I went to Tools > Plugins and clicked on Libnotify Popups to disable it. I think clicked to re-enable it, and pidgin crashed.

ProblemType: Crash
Architecture: i386
Date: Thu Mar 25 10:10:02 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: openafs nvidia
Package: pidgin 1:2.6.6-1ubuntu4
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.26~sched_trace-generic
SegvAnalysis:
 Segfault happened at: 0x2cb01cb <notify_get_server_caps+235>: mov 0x8(%eax),%eax
 PC (0x02cb01cb) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 notify_get_server_caps () from /usr/lib/libnotify.so.1
 ?? () from /usr/lib/purple-2/pidgin-libnotify.so
 purple_plugin_load () from /usr/lib/libpurple.so.0
 ?? ()
 IA__g_cclosure_marshal_VOID__STRING (closure=0x9a456f8,
Title: pidgin crashed with SIGSEGV in notify_get_server_caps()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare staff sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #537208, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.