This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Upgrading from 1.4.0a to 1.4.3+ leads to duplicate songs in collection?

Tags: None
(comma "," separated)
jarel
Registered Member
Posts
2
Karma
0
Hi,

I've recently upgraded from amarok 1.4.0a to 1.4.3 and (then 1.4.4), and I'm having collection woes:

* On first run, the new version rebuilds my collection etc., and seems to be fine

* When I add new music, the new songs are detected and are added to the collection

But:

* All other albums by the same artist (that it's just rescanned) will then have duplicate entries for each track

I've tried scanning through the mailing list archives and this forum, and I couldn't find anyone else having similar problems.  If I've missed something, feel free to point me at it :)

In case it's useful, I'm running AMD64 Gentoo, and I'm not running KDE.  All my music is on an NFS partition mounted at /mnt/net_home.

I've done a bit of poking about in the collection.db database - I have backups from before and after the upgrade, thankfully! - and I've noticed a few things:

* Before the upgrade, the url for a track will start with "/mnt/net_home/jarel/..."

* After the upgrade and initial rebuild, the urls start with "./mnt/net_home/jarel/..." and all entries have a deviceid of -1 (the devices table is empty, too)

* After importing music, the new music has urls starting "./jarel/" and a deviceid of 2, and there are now a couple of entries in the devices table

Unfortunately at this point it's rescanned all the other music in the same parent directory, and also added it to the DB with urls starting with "./jarel", which doesn't match up with the existing "./mnt/net_home/jarel" urls, and so I end up with duplicates.

I'm not sure whether this is something specific to my setup, or a bug in amarok, or just me doing something dumb.  But I'm not able to use amarok until I get it sorted out somehow, so I'd greatly appreciate any help.
jarel
Registered Member
Posts
2
Karma
0
Just a little extra info, as I found a work-around that let me upgrade:

I've found that if I do the following:

- restore my amarok files from 1.4.0a
- run Konqueror (and leave it running)
- run the command "dcop kded mediamanager fullList" (until I get a list of shares)
- start amarok 1.4.4

... then it updates successfully, with the 'devices' table properly populated and matching deviceid values in the 'tags' table.

I guess there's some component of KDE that needs to be running for amarok to properly find the shares.  Would it be possible for amarok to make sure that this service is running before it migrates the collection data?


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot], Yahoo [Bot]