amarok upgrade clears collection

[BonBonTheJon]

Binary package hint: amarok

After upgrading Kubuntu Edgy to Feisty, started amarok, the collection was empty.

amarok 1.4.5 on edgy and feisty

[Pekka Jääskeläinen (pekka-jaaskelainen)]

Confirmed. Although this is not very serious, as rescanning the collection brings back the statistics etc. so the old DB is not completely cleared in the upgrade.

[Ivan Lucas (ivan-lucas)]

I can confirm this as well. I'm using MySQL to store my collection I wonder if this is related. Again for me rescanning the collection cured it.

[Marco Cimmino (cimmo)]

in my case all covers seems lost after rescanning there weren't

[Andrew Ash (ash211)]

I'm not quite sure what the case is here. The only reason the collection would be blanked out during an upgrade is if the files in ~/.kde/share/apps/Amarok or ~/.kde/share/config/amarokrc were deleted. Is this what happens during dist-upgrades? It probably also depends on what database is being used - postgresql, mysql, sqlite.

Either way, there isn't quite enough information here for a developer to work on a fix - https://wiki.ubuntu.com/Bugs/Status - so the status shouldn't be confirmed.

[BonBonTheJon (jonathan-mueller)]

I don't know about what changed in the package, but I know I was using sqlite for the database.

[Andrew Ash (ash211)]

The sqlite database is stored at ~/.kde/share/apps/amarok/collection.db, but others like postgresql and mysql are stored wherever you have the server set up. I wouldn't think upgrading packages in feisty->gutsy or other would clear that, but to be honest, I'm not really sure why this would happen.

It's difficult to troubleshoot without running a bunch of upgrade tests. Losing covers, which are stored in ~/.kde/share/apps/amarok/albumcovers/*, may also be from something going on in the database not realizing that covers are available. Sorry I can't be more of a help.

[Mario Young (mayeco)]

Thank you for the bug report, BonBonTheJon. There is now a newer version of Amarok out, 1.4.7. Can you replicate this problem in the newer version?)

[BonBonTheJon (jonathan-mueller)]

I'm running Gutsy now and have not had any problems since the initial bug report.

[Mario Young (mayeco)]

Dear Jonathan:

Should we mark this bug as Fix Released?

Thank you!

[Sarah Kowalik (hobbsee-deactivatedaccount)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes, if it's reported as solved.

 status fixreleased

Mario Young wrote:
> Dear Jonathan:
>
> Should we mark this bug as Fix Released?
>
> Thank you!
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHIsA17/o1b30rzoURArnLAKC52CeVMH2bGcoyEf49PSRm6F7+hQCfSpAg
YCmiOILbFTMx9zOdB/WWeP4=
=G14v
-----END PGP SIGNATURE-----