pidgin crashed with SIGSEGV in __xmlRaiseError()

[Adam Stovicek]

Binary package hint: pidgin

adam@obsidian:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
adam@obsidian:~$ apt-cache policy pidgin
pidgin:
  Installed: 1:2.5.5-1ubuntu6
  Candidate: 1:2.5.5-1ubuntu6
  Version table:
 *** 1:2.5.5-1ubuntu6 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status
     1:2.5.5-1ubuntu5 0
        500 http://aegis jaunty/main Packages
adam@obsidian:~$

Just grabbed the latest and pidgin segfaults. With the original .purple directory, I got the following in dmesg:
[ 72.021127] pidgin[3990]: segfault at 7fd99dfaac30 ip 00007fd99dfaac30 sp 00007fffbfe1c618 error 14 in libgvfsdbus.so[7fd99dddd000+1ff000]

After renaming the .purple directory to start fresh, I put in my Google Talk details and got the following:
[ 274.270380] pidgin[4550]: segfault at 7fc399f2cc30 ip 00007fc399f2cc30 sp 00007fffbbd9e568 error 15 in 365b55f210c0a22e9a19e35191240f32-x86-64.cache-2[7fc399f1a000+2e000]

Removed .purple, started fresh. Used a Yahoo account with no issue. Added Google account and it segfaults just after connecting with:
pidgin[4942]: segfault at 7f5b68f86c30 ip 00007f5b68f86c30 sp 00007fff8adf65c8 error 15 in 365b55f210c0a22e9a19e35191240f32-x86-64.cache-2[7f5b68f74000+2e000]

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Disassembly: 0x7fd99dfaac30:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.5-1ubuntu6
ProcCmdline: pidgin
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 __xmlRaiseError () from /usr/lib/libxml2.so.2
 ?? () from /usr/lib/libxml2.so.2
 ?? () from /usr/lib/libxml2.so.2
 xmlParseElement () from /usr/lib/libxml2.so.2
Title: pidgin crashed with SIGSEGV in __xmlRaiseError()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.