Summary: | Playlist uses inadequate key for album cover art cache | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Matt Whitlock <kde> |
Component: | Playlist | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 2.2.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Matt Whitlock
2009-11-08 22:01:11 UTC
*** This bug has been marked as a duplicate of bug 170146 *** Myriam, I hope you read my report before you marked it as a duplicate. I specifically made the case for why this is unrelated to the problem described in bug 170146. And why would this not be related? Both the collection and the playlist use the same data. I could be way off base, but it seems like bug 170146 is about an inadequacy in the database representation of album covers. My point is that the database apparently has it correct, at least as of Amarok 2.2.0, since the correct album cover is displayed in the "Current Track" plasmoid while the track is playing, but Amarok's in-memory album cover cache is using an insufficient key, such that cache entries for multiple distinct albums are colliding. If my interpretation of bug 170146 is incorrect, then I apologize for all the noise I've been making. Regardless, all that matters is that you know what's wrong. Thanks for looking into it. Matt, we did some changes to the cover handling in 2.2.1. Please stay tuned for this version, then test again. Thanks :) |