Banshee BPM detection get stucks on missing file

[Jerry Chong]

Binary package hint: banshee

Only a minor annoyance, but when Banshee tries to apply BPM detection on a music library entry that has actually been deleted from the filesystem, the BPM detection extension appears to get stuck and no longer process any further entries.

Debug console output:

[Debug 23:24:26.972] GStreamer running beat detection on /home/.../.../<MP3 file.mp3>
[Debug 23:24:30.329] Saving BPM of 62 for file:///home/.../.../<MP3 file.mp3>
[Debug 23:24:30.408] GStreamer running beat detection on /home/.../.../<MP3 file.mp3>
-- stops here --

Only after removing the file from the library and then restarting Banshee does the extension continue. (There was a Gstreamer error about error analyzing the file's BPM, but unfortunately I didn't manage to capture it.)

ProblemType: Bug
Architecture: i386
Date: Mon Nov 16 23:22:25 2009
DistroRelease: Ubuntu 9.10
Package: banshee 1.5.1-1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: banshee
Uname: Linux 2.6.31-15-generic i686

[Chow Loong Jin (hyperair)]

Could you provide the full console output including the Gstreamer error please?

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
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".