Missing library file handling is broken (another reason for "bpm detection never stops")

Bug #880233 reported by PeterPall
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Banshee
New
Medium
banshee (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

Symptom:
 - bpm detection never stops
 - song similarity detection never stops
 - the first time this happens the console claims that a mp3 or ogg file is missing then stops doing this
 - in the lower right corner of the banshee window a throbber turns indefinitely eating up about 12% of CPU power on a intel atom singlecore device

How to reproduce:
 - import new music to your library
 - use easytag, nautilus or the console to rename or delete the file before bpm detection and similarity detection for this file has finished. If you have a fast system it is perhaps best to deactivate these features first
 - enable the bpm detection and similarity detection again

Another way to trigger the problem:
 - Buy music from the ubuntuone music store
 - move it from "~/.ubuntuone/Purchased From Ubuntu One" to the music library

Activating the "re-scan music library" feature or plug-in or trying to trigger a music library re-scan manually doesn't fix the problem

Expected behavior:
 - If music is missing the respective files will be ignored but information about them is kept in the library: There is a chance that tey reside on an external memory that is currently not plugged in but that might return any moment. For details see the documentation of rhythmbox and shotwell that both work this way.

There is another bug report that nearly the same symptoms will be triggered by having non-audio files (e.G. text files) in the library but I expect it to really be a separate bug.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.2.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: nvidia wl
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Sun Oct 23 10:07:46 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/banshee/Banshee.exe
InterpreterPath: /usr/bin/mono
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LC_TIME=de_DE.UTF-8
SourcePackage: banshee
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
PeterPall (peterpall) wrote :
Changed in banshee:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in banshee (Ubuntu):
status: New → Confirmed
Changed in banshee (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Si Dedman (si-dedman) wrote :

FWIW: before migrating to banshee from rhythmbox (recently) I BPM tagged all my files with BPM Analyser (window program) so all but the 8 .ape tracks in my ~35000 track library are tagged, yet it still goes on forever. Dunno if that's useful intel but thought I'd mention it just in case.

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.