Bug 198861

Summary:	Duplicate collection entries after managing files
Product:	[Applications] amarok	Reporter:	M. Thomas Frederiksen <mahasamoot>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	tseeker
Priority:	NOR
Version:	2.3-GIT
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	This is a screen shot showing the problem

Description M. Thomas Frederiksen 2009-07-04 05:52:35 UTC

Version:           2.2-SVN (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-11-generic

After renaming an artist and selecting "organize files," the collection still shows the old entry.  To fix it, I even did an "rm -rf .kde/share/apps/amarok/mysqle" but to no avail.  I've seen this problem in 2.1.1 and it's still in 2.2 svn.

Comment 1 M. Thomas Frederiksen 2009-07-04 05:54:00 UTC

I should also mention that I deleted the old directories where the mislabeled files had been.

Comment 2 M. Thomas Frederiksen 2009-07-04 05:55:33 UTC

Created attachment 35031 [details]
This is a screen shot showing the problem

Comment 3 Myriam Schweingruber 2009-08-11 15:40:34 UTC

Is this only when you change the name of bands referred to as either 'Bandname' or 'The Bandname'? Then it is a duplicate of bug 176670

Comment 4 Myriam Schweingruber 2009-08-11 15:41:55 UTC

Just forgot: make sure you use the git sources now, we switched to git since about a month.

Comment 5 Emmanuel Benoit 2009-09-13 16:18:29 UTC

I seem to be having this problem since I upgraded to 2.1.80 then to 2.2-GIT.

Comment 6 Emmanuel Benoit 2009-09-13 16:24:52 UTC

Actually, the bug appeared after I rescanned the collection; after I restarted Amarok, it was gone. Strangely, the "recently added albums" was displaying erroneous entries at the same time (i.e. the albums didn't match the artist), which is quite possibly related.

Comment 7 Myriam Schweingruber 2009-10-17 13:39:57 UTC

Marking as a duplicate of bug 210837, since there is a patch

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