Banshee.exe crashed with SIGABRT

Bug #925856 reported by Mark Rooney
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running the latest version of Banshee on Ubuntu 12.04 Alpha 2.
Playback was intermittant and often stalled then Banshee crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: banshee 2.3.4.ds-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 3 15:07:23 2012
Disassembly: => 0x7f4014fbe3b5: Cannot access memory at address 0x7f4014fbe3b5
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
Signal: 6
SourcePackage: banshee
Stacktrace:
 #0 0x00007f4014fbe3b5 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f4015df3d48
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 40 (LWP 9368):
 #0 0x00007f3fabb5cfbd in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f3f9a7fc568
Title: Banshee.exe crashed with SIGABRT
UpgradeStatus: Upgraded to precise on 2012-01-20 (13 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mark Rooney (rooney-mark-a) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f4014fbe3b5 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f4015df3d48
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in banshee (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

iproute version 20111117-1 required, but 20111117-1ubuntu1 is available
makedev version 2.3.1-89ubuntu1 required, but 2.3.1-89ubuntu2 is available
libgtk-3-common version 3.3.10-0ubuntu3 required, but 3.3.12-0ubuntu1 is available
libxcb-shm0 version 1.7-4 required, but 1.8-1 is available
libxcb-render0 version 1.7-4 required, but 1.8-1 is available
outdated debug symbol package for libv4l-0: package version 0.8.5-6ubuntu1 dbgsym version 0.8.5-3ubuntu2
libglib2.0-0 version 2.31.12-0ubuntu1 required, but 2.31.14-0ubuntu1 is available
libxcb1 version 1.7-4 required, but 1.8-1 is available
libgtk-3-0 version 3.3.10-0ubuntu3 required, but 3.3.12-0ubuntu1 is available
debianutils version 4.1 required, but 4.1ubuntu1 is available
libgtk-3-bin version 3.3.10-0ubuntu3 required, but 3.3.12-0ubuntu1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.