Bug 195706

Summary:	bad album names after change and refresh of collection (after restart of amarok everything is good)
Product:	[Applications] amarok	Reporter:	krun <krystian>
Component:	Collection Browser	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	jonny.privateproperty
Priority:	NOR
Version First Reported In:	2.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description krun 2009-06-08 21:03:01 UTC

Version:           2.1 (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

When i changing (to completely other) collection directory and rescaning it, there is problem with displaying album names, if count of new positions is bigger than old then few albums has correct names but as many as was in old collection is wrong.

Artist is the same (i accidentally select all my music and assign them to one artist and now changing collection directories by artist directory and rewriting correct artist name, try do the same and u should have the same effect)

Comment 1 jonny sutton 2009-06-09 13:13:30 UTC

I have experienced a similar problem. Here is what I did: ripped a new CD. waited for amarok to load into collection (approx 30mins), amarok did not find it although folder watching is enabled, clicked update collection, the album was found - but - amarok messed up the albums that hundreds of songs belonged to, ie, cover art remained correct but album name and year were corrupted. on closer inspection the actual ID3 tags were not corrupted, just amaroks own database. The only solution I could find to this was moving the collection to a blank folder and then starting from scratch with "rescan collection." Rescanning the collection without first emptied it as I've just said did not fix this bug, neither did a restart of amarok or a complete PC reboot.

Comment 2 jonny sutton 2009-06-09 13:24:21 UTC

is this a similar or the same problem https://bugs.kde.org/show_bug.cgi?id=186169 ?

Comment 3 Myriam Schweingruber 2009-06-13 12:02:43 UTC


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