Banshee.exe crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()

Bug #757800 reported by AEGonzalez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: banshee

Benshee crashed when lock the screen....Ubuntu Natty beta 1, Unity and Nvidia drivers.

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
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Mon Apr 11 13:46:19 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110408)
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: 0x3a868c <vfprintf+1324>: mov %edi,(%esp)
 PC (0x003a868c) ok
 source "%edi" ok
 destination "(%esp)" (0x00111f5c) in non-writable VMA region: 0x00111000-0x00112000 ---p None
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None
Signal: 11
SourcePackage: banshee
StacktraceTop:
 ?? () from /usr/lib/liboverlay-scrollbar-0.1.so.0
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: Banshee.exe crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
AEGonzalez (andresenriquegonzalez) wrote :
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 754927, 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.