Banshee.exe crashed with SIGSEGV

Bug #755451 reported by Daniel Planas Armangue
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: banshee

banshee stop working

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
Architecture: i386
Date: Sat Apr 9 12:59:23 2011
Disassembly: => 0x24968c: No se puede acceder a la memoria en la dirección 0x24968c
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101202)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_ES.UTF-8
 LANGUAGE=es_ES:es:en_GB:en
SegvAnalysis:
 Segfault happened at: 0x24968c: No se puede acceder a la memoria en la dirección 0x24968c
 PC (0x0024968c) ok
 source "0x24968c" (0x0024968c) ok
 Stack memory exhausted (SP below stack segment)
 SP (0x00d72f1c) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: banshee
Stacktrace:
 #0 0x0024968c in ?? ()
 No symbol table info available.
 No se puede acceder a la memoria en la dirección 0xd72f1c
StacktraceTop: ?? ()
Title: Banshee.exe crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Daniel Planas Armangue (daniplanas.a) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Victor Vargas (kamus) wrote :

Please could you run in a terminal 'banshee --debug' and attach all the output information (while you are trying to reproduce this issue)?, also attach your '~/.config/banshee-1/log' file as a separated attach, Thanks.

visibility: private → public
Changed in banshee (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in banshee (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers