Banshee.exe crashed with SIGSEGV in g_main_context_dispatch()

[vininim]

Binary package hint: banshee

After setting up last.fm scrobbling plugin authentication, I get this bug.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: banshee 2.0.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sun Apr 10 23:28:46 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x14d68c <_IO_vfprintf_internal+1324>: mov %edi,(%esp)
 PC (0x0014d68c) ok
 source "%edi" ok
 destination "(%esp)" (0x0064ff5c) in non-writable VMA region: 0x0064f000-0x00650000 r-xs /var/cache/fontconfig/9451a55048e8dbe8633e64d34165fdf2-le32d4.cache-3
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA /var/cache/fontconfig/9451a55048e8dbe8633e64d34165fdf2-le32d4.cache-3
Signal: 11
SourcePackage: banshee
StacktraceTop:
 ?? () from /usr/lib/liboverlay-scrollbar-0.1.so.0
 ?? () from /usr/lib/liboverlay-scrollbar-0.1.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: Banshee.exe crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to natty on 2011-04-10 (0 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

[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 #754369, 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.