Banshee.exe crashed with SIGABRT

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

Bug Description

Binary package hint: banshee

Banshee was closing unexpectedly after one song had been played. after Restarting the program it froze directly

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: Sat Apr 9 20:16:12 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:en
Signal: 6
SourcePackage: banshee
StacktraceTop:

Title: Banshee.exe crashed with SIGABRT
UpgradeStatus: Upgraded to natty on 2011-04-01 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
lostprophet (matze-spam1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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