Banshee.exe crashed with SIGABRT

Bug #756605 reported by wayman
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Banshee
Invalid
Undecided
Unassigned
banshee (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: banshee

Banshee.exe crashed with SIGABRT

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: Sun Apr 10 18:32:05 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=ru_RU.UTF-8
 LANG=en_US.UTF-8
 LANGUAGE=ru_RU:en_US:en
Signal: 6
SourcePackage: banshee
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Banshee.exe crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
wayman (kotpes) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _wapi_lookup_handle (handle=0xa, type=WAPI_HANDLE_FILE, handle_specific=0xbf4d504c) at handles.c:712
 file_read (handle=0xa, buffer=0xc4410, numbytes=1000, bytesread=0xbf4d50cc, overlapped=0x0) at io.c:348
 ReadFile (handle=0xa, buffer=0xc4410, numbytes=1000, bytesread=0xbf4d50cc, overlapped=0x0) at io.c:2261
 ves_icall_System_IO_MonoIO_Read (handle=0xa, dest=0xc4400, dest_offset=0, count=1000, error=0xbf4d5160) at file-io.c:705
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in banshee (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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
Changed in banshee:
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
Changed in banshee:
status: Incomplete → Invalid
Revision history for this message
druisan (druisan) wrote :

Also happens in x84_64 Ubuntu editions.

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.