Summary: | old collection lost after upgrade to 2.4.0.90 | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Vadym Krevs <vkrevs> |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | mitchell, ralf-engels |
Priority: | NOR | ||
Version: | 2.4.0.90 | ||
Target Milestone: | 2.4.1 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.6 |
Description
Vadym Krevs
2011-03-23 17:01:45 UTC
Very strange. From which Amarok version did you upgrade? The latest shipped with KDE SC 4.5.5 for openSUSE 11.3 from OBS: 2.4.0. Basically, amarok worked fine under openSUSE 11.3 and KDE SC 4.5.5, then I upgraded to 11.4, and then switched to KDE SC 4.6.1 from http://download.opensuse.org/repositories/KDE:/Release:/46/openSUSE_11.4/, and ran amarok for the first time under 11.4, which was when the problem happened. I guess your hard disk UUID got updated when updating KDE which triggers a re-scan. We have already a bug entry for that. What puzzles me is that you have lost artist and album information. Don't you have this information in id3 tags? Can you check one of the offending files. Maybe execute he amarok_collectionscanner on the directory. I did have this information in id3 tags - as the previous version of amarok (and songbird/banshee) always displayed them correctly. However, when it happened with the latest amarok, I went through each file, clicked on "Edit Track Details" and recovered "missing" information using the filename, and saved it back to the file. In other words, the "offending" files are no longer "offending". This is an automated message from the triager: Amarok 2.4.1 has been released on May 8 already. Could you please upgrade and test if you can still reproduce this bug? Without feedback within a month we will close this bug as resolved. Thank you for your understanding. As my old collection was lost during the upgrade, and a new one had to be re-created from scratch, there is no practical way for me to test this. Perhaps you should add upgrade of collections created in older amarok releases to the set of tests you run prior to releasing a new version of amarok. Noted. We will add this to the testing list. In the meantime I will leave this open and check again later once the testing is started. Thank you for your fast feedback. Added to our testing list: http://amarok.kde.org/wiki/Development/Testing#New_Installation Changing to status REMIND. This is solved in the upcoming Amarok 2.6 where a collection update will be triggered on first start. I also added this to the testing wiki: http://amarok.kde.org/wiki/Development/Testing#Upgraded_Installation |