Banshee.exe crashed with SIGABRT in raise()

Bug #766170 reported by Greg A
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: banshee

Listening to an album. Got within a few seconds of next track but music stopped and interface froze.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: banshee 2.0.0-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Tue Apr 19 16:18:08 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110127)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
Signal: 6
SourcePackage: banshee
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: Banshee.exe crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to natty on 2011-04-06 (13 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Greg A (etulfetulf) wrote :
Revision history for this message
Xavier Bassery (xaba) wrote :

Thanks for your bug report.
Could you please run in a terminal "killall banshee && banshee --debug &> ~/banshee-debug.txt", reproduce the bug and then attach the generated file banshee-debug.txt to this bug report (this file will be in your home folder)?
This will greatly help us in tracking down your problem.

Changed in banshee (Ubuntu):
status: New → Incomplete
Victor Vargas (kamus)
Changed in banshee (Ubuntu):
importance: Undecided → Medium
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.