https://bugs.kde.org/show_bug.cgi?id=511453
--- Comment #6 from Marcos Raul Carot <[email protected]> --- Hi! Thanks for that. I run a full rescan under Collection Folders. It seems that that has fixed it. Thinking of what may have caused the issue, it is possible that I re-tagged the files with Picard MusicBrainz after the first time the collection was scanned. Do you think that's possible? In any case, thank you for your time, and thank you for Amarok :) Cheers, Marcos On Sun, 4 Jan 2026 at 17:54, Tuomas Nurmi <[email protected]> wrote: > https://bugs.kde.org/show_bug.cgi?id=511453 > > --- Comment #5 from Tuomas Nurmi <[email protected]> --- > Thank you for the sample files! However, I am unable to reproduce the issue > even with them (I tried on two systems, one with embedded database and one > with > a stand-alone mariadb server). > Did you happen to have them earlier tagged under same album title? > Amarok not picking up the (externally) changed tags and showing earlier > ones > from database/cache could be one explanation I can come up with. > If that isn't the case, then I'm out of ideas. > > Anyhow, I guess you could try running > > amarokcollectionscanner -r . > > in terminal and seeing if the album info is ok in collection scanner > output. > If yes, then maybe try a full collection rescan (in settings -> database). > > > If problem still persists, (this will reset the stats for the tracks, > unfortunately) move the two albums away from collection, run a collection > update (in tools menu), move albums back in place, and collection update. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
