Bug 208306 - Amarok displays wrong tags in the playlist after a rescan
Summary: Amarok displays wrong tags in the playlist after a rescan
Status: RESOLVED DUPLICATE of bug 214599
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.1.90
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: 2.3.1
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-23 16:47 UTC by Luca Carlon
Modified: 2009-11-23 19:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Carlon 2009-09-23 16:47:34 UTC
Version:           2.1.90 (using KDE 4.3.1)
Installed from:    Ubuntu Packages

I see some cases in which tracks are placed under the correct artist in the collection viewer, but when placed in a playlist, the artist is wrong. In the tag editor the artist is in fact wrong as well. After restarting amarok, everything is fixed.

How to reproduce: it just happened after a new scan. I don't know a deterministic procedure to show this.
Comment 1 Mikko C. 2009-09-23 16:59:22 UTC
yes this is a known bug, it can happen when new tracks are added to the collection, so a rescan is performed.
Comment 2 Jeff Mitchell 2009-09-23 17:12:47 UTC
(In reply to comment #1)
> yes this is a known bug

It is? :-)

Never heard of it before.
Comment 3 Mikko C. 2009-09-23 17:15:55 UTC
isn't this the case where tags aren't refreshed after an update (messed up collection)? but after restarting amarok all is good?
Comment 4 Jeff Mitchell 2009-09-23 17:21:27 UTC
Maybe, but if so it's a new cause -- I fixed the earlier one a while back.
Comment 5 0...0 2009-11-22 16:40:45 UTC
Version:           2.2.1 (using KDE 4.3.3)
Installed from:    Archlinux Packages

I can confirm this bug: When updating the library, some artists are shown with wrong tags (even in the library). After a restart of Amarok the artists are displayed right again.
Comment 6 Myriam Schweingruber 2009-11-23 19:22:48 UTC
A full rescan followed by a restart of Amarok solves that problem in 2.2.1. Can't reproduce this here with Amarok 2.2-git

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