Banshee.exe crashed with SIGSEGV

Bug #644311 reported by "Kosmonaut" Bernd Müller on 2010-09-21
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: banshee

I tried to start a song within banshee....result= crash

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: banshee 1.7.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 21 13:10:00 2010
Disassembly: => 0x7f9a848816da: Cannot access memory at address 0x7f9a848816da
ExecutablePath: /usr/lib/banshee-1/Banshee.exe
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee-1 /usr/lib/banshee-1/Banshee.exe /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.utf8
SegvAnalysis:
 Segfault happened at: 0x7f9a848816da: Cannot access memory at address 0x7f9a848816da
 PC (0x7f9a848816da) ok
 Stack memory exhausted (SP below stack segment)
 SP (0x7f9a6499cfa0) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: banshee
Stacktrace:
 #0 0x00007f9a848816da in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f9a6499cfa0
StacktraceTop: ?? ()
Title: Banshee.exe crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Stacktrace:
 #0 0x00007f9a848816da in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f9a6499cfa0
StacktraceTop: ?? ()
ThreadStacktrace:

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Victor Vargas (kamus) wrote :

Please could you check if this behaviour is still occurring in latest release of Banshee 1.8.0? Thanks in advance.

Changed in banshee (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Victor Vargas (kamus) on 2010-11-03
visibility: private → public
Victor Vargas (kamus) wrote :

Kosmonaut, any news about it?

Hi!

Sorry that I didn't respond earlier. I run Banshee 1.8.0: [Ubuntu 10.10 (linux-gnu, x86_64).

This problem still occurs:

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

This crash only happens when "winbind" is installed (without winbind banshee runs fine)

Victor Vargas (kamus) wrote :

I have noticed that you have already another report more completed with same symptoms, so I will mark this report such a duplicate of bug 641162.

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

Other bug subscribers