Banshee.exe crashed with SIGSEGV

Bug #352444 reported by Rebecca Menessec
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: banshee

Banshee crashed on attempt to close. No music playing other other services obviously being used. Playlist empty. Also got a crash when disabling and re-enabling iPod support, but didn't get a crash capture.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x7fb29ec6f9c2:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/banshee-1/Banshee.exe
InterpreterPath: /usr/bin/mono
Package: banshee 1.4.3-3ubuntu2
ProcCmdline: mono /usr/lib/banshee-1/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: banshee
Stacktrace: #0 0x00007fb29ec6f9c2 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: Banshee.exe crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape vboxusers video

Revision history for this message
Rebecca Menessec (aloishammer-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in banshee (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
visibility: private → public
Revision history for this message
Rebecca Menessec (aloishammer-deactivatedaccount) wrote :

The backtrace instructions for Mono apps aren't real clear. I'm hoping this .crash includes the info you were looking for. I see there's at least a core included. I invoked banshee with 'mono --debug /usr/lib/banshee-1/Banshee.exe'.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

No, this doesn't provide the information we're looking for, sorry. Could you try attaching the output of 'banshee --debug' when that happens? Also, please try to reproduce this on 1.5.0, which is in https://launchpad.net/~banshee-unstable-team/+archive/ppa

Revision history for this message
Jonathan Thomas (echidnaman) 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.