Banshee.exe crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

Bug #728030 reported by Nathaniel Homier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: banshee

Closed the program and a short while later this bug appeared.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: banshee 1.9.4-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Wed Mar 2 13:33:13 2011
Disassembly: => 0x150a958: Cannot access memory at address 0x150a958
ExecutablePath: /usr/lib/banshee-1/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110223)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee-1 /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x150a958: Cannot access memory at address 0x150a958
 PC (0x0150a958) not located in a known VMA region (needed executable region)!
SegvReason: executing 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()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Nathaniel Homier (ubuntu-one-universal-mechanism-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
visibility: private → public
Revision history for this message
Nathaniel Homier (ubuntu-one-universal-mechanism-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Should have added that I'm running Natty in the latest version of Virtualbox. The VM has 4096 ram.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__BOXED (closure=0x8cf80c0, return_value=0x0, n_param_values=2, param_values=0x98edb18, invocation_hint=0xbfd558b0, marshal_data=0x150a958) at /build/buildd/glib2.0-2.28.1/./gobject/gmarshal.c:568
 g_type_class_meta_marshal (closure=0x8cf80c0, return_value=0x0, n_param_values=2, param_values=0x98edb18, invocation_hint=0xbfd558b0, marshal_data=0x7c) at /build/buildd/glib2.0-2.28.1/./gobject/gclosure.c:878
 g_closure_invoke (closure=0x8cf80c0, return_value=0x0, n_param_values=2, param_values=0x98edb18, invocation_hint=0xbfd558b0) at /build/buildd/glib2.0-2.28.1/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=0x8cf8100, detail=0, instance=0x903d278, emission_return=0x0, instance_and_params=0x98edb18) at /build/buildd/glib2.0-2.28.1/./gobject/gsignal.c:3182

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in banshee (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Victor Vargas (kamus) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.