(banshee) Nereid.exe crashed with SIGSEGV

Bug #281547 reported by Cameron Gorrie
6
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: banshee

Since latest update (dist-upgrade), Banshee sporadically (1 time out of 4 or so) crashes between switching tracks (the GUI stops responding and I am forced to kill it). It does not crash other than when automatically going between tracks -- it will be playing a track, the track will finish, and then I'll notice that there's no music, upon which I'll find banshee not responding.

More information:

Description: Ubuntu intrepid (development branch)
Release: 8.10

banshee:
  Installed: 1.2.1-3ubuntu1
  Candidate: 1.2.1-3ubuntu1

Please let me know how I can make this bug report more complete.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/banshee-1/Nereid.exe
InterpreterPath: /usr/bin/mono
Package: banshee 1.2.1-3ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: banshee-1 /usr/lib/banshee-1/Nereid.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
Signal: 11
SourcePackage: banshee
Stacktrace: #0 0x080f1a5e in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: Nereid.exe crashed with SIGSEGV
Uname: Linux 2.6.27-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Cameron Gorrie (sastraxi) 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:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) 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:
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.