Bug 188166

Summary:	Collection goes a-wall after removing one folder from the collection scanner settings
Product:	[Applications] amarok	Reporter:	Piotr <piotrek.juzwiak>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	2.0.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Double covers, no expanding Again, double covers, some not expanding at all, some show the artist but don't expand more while some are double, expand and expand artist's tracks

Description Piotr 2009-03-26 14:49:57 UTC

Version:           2.0.2 (using 4.2.1 (KDE 4.2.1) "release 106", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.29-51-default

After scanning all the folders with music and downloading all the covers i realised i don't want one album in my collection so i opened up settings, collection settings and unticked an album i didn't want. After that the collection gets messed up completely, some albums stay alright some don't show up after clicking the + sign and some play completely other albums (having for example album X with the cover for X you expect music from this album but it plays music from album Y). I fix it by letting amarok scan again by removing the amarok folder (after quitting it) from /home/<user>/.kde4/share/apps/amarok .

Comment 1 Piotr 2009-03-26 15:00:27 UTC

Additionally some show up twice (cover) and from these two some don't expand after clicking + while in some cases one doesn't expand while other is fine.

Comment 2 Piotr 2009-03-26 15:02:41 UTC

Created attachment 32408 [details]
Double covers, no expanding

Comment 3 Piotr 2009-03-26 15:04:30 UTC

Created attachment 32409 [details]
Again, double covers, some not expanding at all, some show the artist  but don't expand more while some are double, expand and expand artist's tracks

Comment 4 Mikko C. 2009-03-26 15:42:32 UTC


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