Bug 207703 - database scrambled, id3 tags are ok but tracks are displayed with different artist and/or album
Summary: database scrambled, id3 tags are ok but tracks are displayed with different a...
Status: RESOLVED DUPLICATE of bug 178973
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.0.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-17 19:13 UTC by kinalus
Modified: 2009-09-17 19:15 UTC (History)
0 users

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 kinalus 2009-09-17 19:13:57 UTC
Version:           2.0.2 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-15-server

Hi,

I recently moved to amarok 2.0 from 1.4, I imported the DB from 1.4 successfully
then rescanned and everything seemed ok for a couple of weeks.

Yesterday I was searching for an album I knew was there but amarok was unable 
to find it searching by artist (although other albums by the same artist appeared) or album name.
I manually found the album and checked it's tags with easytag then proceeded to correct
some of the tags (artist and album name was ok so amarok should have found it) as well as the tags 
and filenames of a couple of other albums with easytag. 
amarok still could not discover the album, although the option 'Watch folders for changes' is on
the affected directories where not rescanned. So I used the 'Rescan Collection' button and that
fixed the problem. 

After restarting amarok my real problem appeared, the track titles in the playlist are correct, 
but the artist and usually the album have taken random values from other artists and albums 
in my collection. The affected files are only the ones that where in my playlist when I restarted amarok. Rescanning the collection does not help although the id3 tags of the affected mp3s appear ok in other programs.

A quick google search reveals this post that describes the same problem.
http://www.reddit.com/r/linux/comments/8pld5/amarok_21_released/c0a1iqw

Sorry for the lengthy post but I don't know how to provide more meaningful information.
Comment 1 Mikko C. 2009-09-17 19:15:43 UTC
fixed in 2.2

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