https://bugs.kde.org/show_bug.cgi?id=381263
--- Comment #4 from Hamidreza Jafari <hamidrjaf...@gmail.com> --- I see. It is just less than a month that I have switched to Amarok. At the beginning I delved into the settings and applied a full scan of the collection. I think I had thought I better turn on the write cover to file option, since prior to reporting this I revisited the settings and noticed it was on. I turned it off (hence "Now") and then reported here. I thought perhaps Amarok has tried to process an already present cover since I always fix tracks with relevant info (including cover) then import into the collection (previously Banshee). I checked some of the problematic tracks and see they have the embedded cover. Thought perhaps it could be troubleshot so that latent problems come forward. Also I think let's reintroduce the collection and check if there was something wrong from batch import. Or not? -- You are receiving this mail because: You are watching all bug changes.
