Banshee.exe crashed with SIGSEGV

[pascal germroth]

tried to click on an album cover

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: banshee 2.1.4-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4
Uname: Linux 3.0.0-11-generic-pae i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Sep 22 21:08:44 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
SegvAnalysis:
 Segfault happened at: 0xb772eef4 <malloc_consolidate+228>: mov 0x4(%esi),%eax
 PC (0xb772eef4) ok
 source "0x4(%esi)" (0x00000003) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: banshee
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: Banshee.exe crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-21 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[pascal germroth (pascal-ensieve)]

the dbus plugin was disabled actually, but when started from the console the debug log still complains about some dbus errors (missing keys etc, I guess the schema has somehow changed, this should not throw uncaught exceptions, but I don't think this here is really a banshee bug, but a native binding?)

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