Bugzilla – Bug 6925
Playlist scan fails due to a problem with importing covert art
Last modified: 2008-02-03 17:52:48 UTC
It would seem that a 'Rescan' for playlists performs a covert art import as part of it's process. In my case, the playlists scan never completes properly. The log shows that during the covert art import, it never makes it past a particular mp3 file. I'm attaching a copy of that mp3 to this bug. I then went and removed the cover art from that mp3 (all my covert art is stored in tags), the scan made it further but failed on another mp3 a little later.
Created attachment 2808 [details] An example of an mp3 that causes covert art importer to fail Here is an example mp3 that causes the covert art scanning / importing during a playlist scan to fail.
After further investigation, I think this is probably yet another duplicate of bug #4699.
Please leave targets and priorities at default. These are for qa and assignee use. To confirm, please edit and re-save the jpg file to the mp3 tag (or simply resave the artwork file with a clean header). The most recent nightlies should have more debugging and capability of checking for invalid files. Try settings logging for artwork to DEBUG.
>> Please leave targets and priorities at default. These are for qa and assignee use. I have no clue what you are saying. As far as I know, I have not changed any targets or priorities so please explain.
I have re-saved the mp3s in question with new cover art and the cover art scan completed successfully.
*** This bug has been marked as a duplicate of 4699 ***
When creating bugs, is would be nice if you did not set the "Target Milestone" or the "Priority". When this report was created, these were set to 7.0 and P1 respectively. Default is for "---" as a target and P2 as priority. After QA does a review, they will set the "Target Milestone" so that developers know when the bug is desired to be fixed. Developers will then set the Priority to match their schedule. Hope that makes it clearer. thanks. Anyway, this one, having been confirmed and marked as a duplicate will now be handled as part of the identified duplicate.