Bug 225862 - Amarok doesn't recognize changes of cover.jpg images in folders
Summary: Amarok doesn't recognize changes of cover.jpg images in folders
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: Tools/Cover Manager (show other bugs)
Version: 2.2.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-07 21:05 UTC by Jan Hofmann
Modified: 2010-12-07 19:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.4


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Hofmann 2010-02-07 21:05:23 UTC
Version:           2.2.2 (using 4.3.5 (KDE 4.3.5), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.32-gentoo-r3

I added a cover.jpg file in every album folder for my existing amarok collection. Then I switched off automatic cover fetch and deleted all covers under [...]amarok/albumcover/large/*.jpg and [...]amarok/albumcover/cache/*.jpg to make sure that only the local covers are used.
After restarting amarok there were no covers at all. Amarok doesn't recognize or show the new covers.

A re-scan of the collection doesn't help.

Solution:

To get the new covers work do the following:
- uncheck all folders in your collection under preferences-> collection
- restart amarok
- Amarok is empty, no song in you collection
- now re-check you collection
- restart amarok
- collection is up again, all ratings and play counts are still there and also the coverart is shown!

So, the cover manager is only looking for coverart inside the folders once at the moment the folder is added to the collection and doesn't track any changes.

I hope my description is understandable, cause my native language is german.
Comment 1 Myriam Schweingruber 2010-02-08 01:10:02 UTC
Not sure this is still a problem in current git, there has been extensive work in the CoverManager since Amarok 2.2.2 was released.
Rick, any input about this?
Comment 2 Rick W. Chen 2010-05-09 13:00:54 UTC
Sorry, I must have missed this somehow.

The cover manager/fetcher atm doesn't look at images on disk; the collection scanner does that. I wrote in BUG:232849 Comment #2 how the current system works.

Currently it's a pain to do what the Jan wants, mostly due to BUG: 223222. I'm going to fix that, then unsetting album covers would be easy. Once that's done, a collection rescan should get those cover.jpg on disk set for the albums. I also want to add the ability to look in the music folder for images to the cover fetcher so that should take care of this use case as well.
Comment 3 Samuel Brack 2010-12-07 16:11:06 UTC
The problem seems to be fixed in 2.4-GIT, since I reproduced the conditions when this bug appeared (I added a cover from the internet in a folder where an album without a cover was, deactivated the download of new covers, deleted the caches and restarted amarok). 
After restarting amarok the new cover and all old covers that are saved on the hard disk were shown by amarok. Only one time (I tested the bug against several albums) I had to do a re-scan of the collection, but after doing that amarok worked like expected.
Comment 4 Myriam Schweingruber 2010-12-07 19:57:55 UTC
Closing as fixed, thanks for testing