Banshee.exe crashed with SIGSEGV

Bug #743560 reported by montun
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: banshee

Trying to play music on built in jamendo

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: banshee 1.9.5-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Sun Mar 27 12:53:45 2011
Disassembly: => 0x2e868c: Cannot access memory at address 0x2e868c
ExecutablePath: /usr/lib/banshee-1/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110326)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee-1 /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_DK.UTF-8
 LANGUAGE=en_DK:en
SegvAnalysis:
 Segfault happened at: 0x2e868c: Cannot access memory at address 0x2e868c
 PC (0x002e868c) ok
 Stack memory exhausted (SP below stack segment)
 SP (0x004fdf5c) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: banshee
Stacktrace:
 #0 0x002e868c in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x4fdf5c
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
montun (montun) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x002e868c in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x4fdf5c
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 :

I am not able to reproduce a crash here but I can't reproduce any stream from jamendo, probably is related to bug https://bugzilla.gnome.org/show_bug.cgi?id=637892

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

montun, any news about this issue? are you still facing this behaviour?

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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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