Bug 114887

Summary: Wrong cover shown (only correct in some fullsize views) when replacing custom cover by amazon cover
Product: [Applications] amarok Reporter: uli9999 <uli.2001>
Component: generalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: normal CC: morrow
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description uli9999 2005-10-22 19:42:50 UTC 
Version:           1.3.3-SVN (22.10.2005) (using KDE KDE 3.4.92)
Installed from:    SuSE RPMs

For a new album with a cover in its directory, Amarok found the cover automatically. Now I want to replace it with the cover from amazon. This works only partly:

In the "Current" tab, both the bigger view at the top and the occurance in the "Compilations with..." part show the old cover.

When I do "show fullsize" at the top, the old cover is shown in fullsize.

When I do "show fullsize" in the "compilations with" part, the new amazon cover is shown. (Very strange...)

In the "Your newest albums" part of the "Home" tab, the old cover is shown.

When I do "show fullsize" here, the new amazon cover is shown.

When I do "edit track information" for a track of the album, the old cover is shown.
Comment 1 Jeff 2005-10-26 04:31:01 UTC 
I am having this same problem except when I try to replace one custom cover with another.

Basically, if I accidently choose the wrong image for the cover, and then try to change it to the correct image, it will still display the thumbnail for the first, even if I unset it.

I am tempted to go and find where it stores the thumbnail but I cannot figure out where that is.

Not a big deal but a bit annoying. I would imagine this would be easy to fix.
Comment 2 richlv 2007-02-14 13:41:44 UTC 
there have been some changes to cover caching lately. is this still happening with 1.4.5 ?
Comment 3 Tobias Knieper 2007-02-14 15:25:16 UTC 
Indeed this seems to be a dup of #130518. If not please reopen.

*** This bug has been marked as a duplicate of 130518 ***