I think it is a problem with Amarok, upsteam issue... They probably change something with the database version that needs a re-scan. It is not really an issue, as long as this bug is available for searching.
I wonder if the package could be scripted to rescan on install of the package: amarokcollectionscanner might do it?
I think it is a problem with Amarok, upsteam issue... They probably change something with the database version that needs a re-scan. It is not really an issue, as long as this bug is available for searching.
I wonder if the package could be scripted to rescan on install of the package: amarokcollectio nscanner might do it?