Hi,

Amarok has the option (via "Settings" => "Configure Amarok" => "Metadata") to "Write statistics to file".

This is nice to have in case the local collection database becomes corrupted or is deleted by the user.

This is now my situation: I want to read back the statistics which Amarok wrote to the files into a new collection.

How do I do this?

Thanks,
Ulrich

Did you try? In my understanding this should just work.

Hi,


thanks for the fast reply!

Yes, I tried - indeed I just now noticed that the ratings and other statistics are in fact still there.

Which makes my original question irrelevant, I guess.

The new issue now is that the ratings are not displayed any more in the playlist or in the track information (via the context menu). The rating-stars are displayed in all-grey, except in the pop-up display when hovering the mouse over the Amarok icon on the KDE status bar.
I even tried Amarok compiled from git master - no difference, so it seems the problem is with one of the KDE libs.

Apparently, Ubuntu messed up one of the recent updates to the KDE libraries in the 15.04 testing repositories.
I will wait a few days; maybe it gets fixed. If not, I will write a bug report in Ubuntu.


Regards,
Ulrich

I had the same problem with the rating stars not displaying correctly in Amarok. Switching the system icon theme from Breeze back to Oxygen fixed it for me.

Sadie wrote:...
The new issue now is that the ratings are not displayed any more in the playlist or in the track information (via the context menu). The rating-stars are displayed in all-grey, except in the pop-up display when hovering the mouse over the Amarok icon on the KDE status bar.
I even tried Amarok compiled from git master - no difference, so it seems the problem is with one of the KDE libs.

Apparently, Ubuntu messed up one of the recent updates to the KDE libraries in the 15.04 testing repositories.
I will wait a few days; maybe it gets fixed. If not, I will write a bug report in Ubuntu.

Not Ubuntu, but a problem with the Breeze theme, there already is a bug report for this IIRC.

Sean and Mamarok,

many thanks - you are right. Changing the system icon set to Oxygen works for me.

https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1445693

I did never change the theme to "Breeze" though - it came with the system installation.

Apparently, Amarok and the Breeze theme are not supposed to work together without
modifications, so the Ubuntu bug was changed to "invalid"...

Because it is not a Kubuntu bug. You installed Kubuntu 15.04 that ships Plasma5, and Breeze is the default theme for Plasma5, nothing surprising in that.
So the bug is filed on bugs.kde.org for the Breeze theme, reporting this against Kubuntu is wrong, as only bugs specific to the distribution should be reported there, and this one is not specific to the distribution.

Mamarok wrote:[...] reporting this against Kubuntu is wrong, as only bugs specific to the distribution should be reported there, and this one is not specific to the distribution.

What I actually intended by reporting this on Launchpad.net instead on the KDE bugtracker was to make things easier for the KDE guys.

It should be Canonicals responsibility to deliver a working product, no matter if the problem lies in an upstream component. And that would mean doing the necessary investigation and upstream reporting.

At least that is the ideal situation with a responsible supplier who actually cares about his products..

By marking the bug as "invalid" on their bugtracker, the responsible person at Ubuntu also prevents the affected users from tracking the issue through the hierarchy of the product, likely leading to duplicate bug submissions or worse effects, like frustrated users..
I realise that the Amarok developers have a deeper understanding of the dependencies of the product and might not need that kind of information. But I as the user don't have that information.

I am the person who marked the bug as invalid on Launchpad, as it is a bug in Breeze, not in Kubuntu. It will appear on all distros using Breeze and it is not the responsibility of the distribution developers to fix upstream bugs, that is not how this works

So please, do not report bugs on Launchpad that are clearly caused by upstream, not by modifications made by the distribution.