Bug 1866

Summary:	Amarok collection scanner having a problem with UUIDs causing database loss (play count, statistics, etc.)
Product:	Mageia	Reporter:	Edward d'Auvergne <true.bugman>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	stormi-mageia
Version:	1
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Edward d'Auvergne 2011-06-20 10:27:39 CEST

Description of problem:

When moving from Mandriva 2010.0 to Mageia 1 (using a new install, but keeping /home), the Amarok collection scanner throws a hissy fit and wipes out the collection information (as every single Amarok upgrade from 1.1 has done to me).  This is simply this bug, as reported upstream:

https://bugs.kde.org/show_bug.cgi?id=265567

Howevery they say it is fixed in 2.4.1, the version that comes with Mageia 1, but the database is still lost.  The relevant debugging print outs appear to be:

amarok:     [SqlScanResultProcessor] deleteTrack "amarok-sqltrackuid://fbe47fa74f1341dd962198f967dd7b28" url id 4233 
amarok:     [SqlScanResultProcessor] deleteTrack "amarok-sqltrackuid://74c7a31e9d8f8a374489c5dca0a66ec6" url id 4232 
amarok:     [SqlScanResultProcessor] deleteTrack "amarok-sqltrackuid://1a91a7cf8b5a7c447b015c7dd26941f6" url id 4231 
amarok:     [SqlScanResultProcessor] deleteTrack "amarok-sqltrackuid://fe4e5fbe84a4f148814e5b4e6f6237d4" url id 4230 

repeated for every single track and then later:

amarok:     [WARNING] [SqlScanResultProcessor] Found urls entry without directory. A phantom track. Removing "amarok-sqltrackuid://8cadba6c5862354ef9f00516659ff12c" 
amarok:     [SqlScanResultProcessor] deleteTrack "amarok-sqltrackuid://8cadba6c5862354ef9f00516659ff12c" url id 1 
amarok:     [WARNING] [MountPointManager] Device  0  not in database, this should never happen! 
amarok:     [WARNING] [SqlScanResultProcessor] Found urls entry without directory. A phantom track. Removing "amarok-sqltrackuid://7a2dab68f5b34395d687c28a00ef7620" 
amarok:     [SqlScanResultProcessor] deleteTrack "amarok-sqltrackuid://7a2dab68f5b34395d687c28a00ef7620" url id 2 
amarok:     [WARNING] [MountPointManager] Device  0  not in database, this should never happen! 

again repeated for each track.  After this, the stats and other meta data is lost.

Version-Release number of selected component (if applicable):

amarok-2.4.1

How reproducible:

100%

Steps to Reproduce:
1.  Restore an old amarok database into ~/.kde4/share/...
2.  Open amarok.
3.  Wait for the collection scanner to kick in.  Before this the metadata is present.
4.  After the collection scanner starts, the local collection drops to 0 tracks.
5.  Performing a 'full rescan' adds all tracks back with covers, but the metadata not stored in the music files is lost.

Comment 1 Edward d'Auvergne 2011-06-20 13:12:58 CEST

This seems to be self resolving after deleting all Amarok configuration files in ~/.kde4/share/config (also restoring the old Amarok collection, i.e. all the backed up ~/.kde4/share/apps/amaraok files).  The collection scanner reaches 99% and then runs at 100% of the CPU for ~20 min.  After that, Amarok is happy and the metadata survives.  This bug could probably be closed.  It's a pity Amarok isn't more fail-safe.  I hope this one doesn't cause upgrading users to permanently loose their music collection metadata.

Comment 2 Samuel Verschelde 2011-10-01 09:59:47 CEST

Closing according to comment #1, thanks !

CC: (none) => stormi
Resolution: (none) => FIXED
Status: NEW => RESOLVED