Due to a change in liblastfm 1.0.7, track scrobbling no longer works in Amarok 2.7.1. This was just fixed upstream in Amarok, the upstream bug has a link to the git commit: https://bugs.kde.org/show_bug.cgi?id=320219 Reproducible: Steps to Reproduce:
CC: (none) => balcaen.john, fundawang, nicolas.lecureuil
CC: (none) => juan.baptisteAssignee: bugsquad => juan.baptiste
Amarok 2.7.1 is available on the repos, please update it and test again.
This bug wasn't fixed upstream until *after* 2.7.1.
Oops, my bad.
@David, do you know if this issue is also present on mga 3 2.7.0 package ?
Status: NEW => ASSIGNED
(In reply to Juan Luis Baptiste from comment #4) > @David, do you know if this issue is also present on mga 3 2.7.0 package ? Technically yes, but as Mageia 3 shipped with liblastfm 1.0.6, you don't see the issue. Mageia 3 users will only have the problem if they backport and install liblastfm 1.0.7 themselves.
Ok, there's an updated package with the patch from the upstream report, please test and report back.
this amarok update will be part of KDE 4.10.4 update 'pack'
(In reply to Nicolas Lécureuil from comment #7) > this amarok update will be part of KDE 4.10.4 update 'pack' You mean for mga 3 I suppose ?
I think Nicolas just got the bugs confused. Bug 10341 and Bug 10480 are regarding the Amarok 2.7.1 update candidate for Mageia 3. This bug is a Cauldron-only issue and no update for Mageia 3 will be needed for it. If any users backport liblastfm 1.0.7 to Mageia 3, they can backport this patch too.
(In reply to Juan Luis Baptiste from comment #6) > Ok, there's an updated package with the patch from the upstream report, > please test and report back. Thanks. You may marked this bug as FIXED then, unless someone else can test Amarok with last.fm on Cauldron right now. I won't be able to test it anytime soon.
Ok, closing then.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED