Bug 196094 - Rescanning collection seems to mix tracks of different artists
Summary: Rescanning collection seems to mix tracks of different artists
Status: RESOLVED DUPLICATE of bug 178973
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 22:13 UTC by Marcus Harrison
Modified: 2009-06-12 08:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Harrison 2009-06-11 22:13:53 UTC 
Version:           2.1 (using 4.2.4 (KDE 4.2.4), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.29-gentoo-r3

In my collection, Amarok has started to behave strangely: for example, one artist has an album that is not theirs, but someone elses, under their name, but the tracks in that album still belong to that artist (i.e. "Jami Sieber" --> "Brave New World" (and Iron Maiden album) --> "9 - Broken Open" (one of Jami Sieber's songs)). In some cases, the albums simply don't show any tracks under them at all. I checked in Dolphin, and the files are still there and untouched.

I think this is related to the, "Settings --> Configure Amarok --> Collection --> Rescan Collection" button.
Comment 1 Marcus Harrison 2009-06-11 22:16:39 UTC 
Sorry, I'll correct myself: I know it's related to the, "Rescan Collection" button. I have removed everything in .kde/share/apps/amarok, and when I started amarok it has correctly scanned and ordered the collection. Automatic re-scanning when something has changed seems to work as well. All that is wrong is that button.
Comment 2 Myriam Schweingruber 2009-06-12 08:26:47 UTC 
You mean, "rescanning collection" mixes up your collection, right? Changed the title accordingly
Comment 3 Mikko C. 2009-06-12 08:37:22 UTC 

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