Banshee.exe crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

[Lindinaldo]

Binary package hint: banshee

when trying listen music

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: banshee 1.9.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Wed Jan 26 05:42:23 2011
Disassembly: => 0x525c818: Não é possível acessar a memória no endereço 0x525c818
ExecutablePath: /usr/lib/banshee-1/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101202)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee-1 /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=pt_BR.utf8
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en_GB:en
SegvAnalysis:
 Segfault happened at: 0x525c818: Não é possível acessar a memória no endereço 0x525c818
 PC (0x0525c818) not located in a known VMA region (needed executable region)!
 source "0x525c818" (0x0525c818) not located in a known VMA region (needed readable region)!
SegvReason:
 executing unknown VMA
 reading unknown VMA
Signal: 11
SourcePackage: banshee
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__BOXED () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: Banshee.exe crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 g_type_class_meta_marshal (closure=0xb76e15a0,
 g_closure_invoke (closure=0xb76e15a0, return_value=0x0,
 signal_emit_unlocked_R (node=0xb76e15e0, detail=0,
 g_signal_emit_valist (instance=0xb0c84c80, signal_id=18,

[Victor Vargas (kamus)]

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