pidgin crashed with SIGSEGV in purple_signal_emit_vargs()

[lorimer]

2 computers running 13.04. Pidgin crashes on both. Reinstalled 1 and even with a clean install, it still crashes. Tried moving the .purple directory to start clean on other, same problem.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: pidgin 1:2.10.7-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 19 10:11:18 2013
ExecutablePath: /usr/bin/pidgin
InstallationDate: Installed on 2013-01-25 (24 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130122)
MarkForUpload: True
ProcCmdline: pidgin
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe8618a26ab: repz cmpsb %es:(%rdi),%ds:(%rsi)
 PC (0x7fe8618a26ab) ok
 source "%es:(%rdi)" (0x7fe8618a3ca9) ok
 destination "%ds:(%rsi)" (0x00000040) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/pidgin/cap.so
 ?? () from /usr/lib/pidgin/cap.so
 purple_signal_emit_vargs () from /usr/lib/libpurple.so.0
 purple_signal_emit () from /usr/lib/libpurple.so.0
 purple_blist_update_buddy_status () from /usr/lib/libpurple.so.0
Title: pidgin crashed with SIGSEGV in purple_signal_emit_vargs()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (Do:29036): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (process:29240): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1133119, 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.