Amarok and last.fm scrobbling problem

[Tuomas Nurmi]

Hi Martin

That's unfortunate to hear. I had no problems with scrobbles during the re-work
of the last.fm plugin connection mechanism, and neither haven't had after that
(I'm on Tumbleweed, too). I think I didn't use the old and the new mechanism
simultaneously, though, so I guess it is not totally impossible that having two
different kind of Amarok connections would confuse Last.fm somehow, albeit I don't
think that's very likely.

Can you try running `amarok --debug-with-lastfm` and seeing what kind of last.fm
related messages are there in the console output? 
I think the relevant ones are ones with tags [lastfm] or <lfm, or any warnings with
"last.fm error"

e.g. on change of track, I get
amarok: [lastfm] nowPlaying: 
which is followed by a last.fm response that starts with
<lfm status=\"ok\">\n    <nowplaying>

and after a track finishes, I get a
[lastfm] scrobble:

(please note that due to a bug in liblastfm, running `amarok --debug` breaks everything;
one indeed has to use --debug-with-lastfm to keep last.fm connection intact)

Best regards
Tuomas


Martin Byttebier kirjoitti tiistaina 30. heinäkuuta 2024 21.43.40 UTC+3:
> Hello,
> 
> Since 21 july scrobbling seems not to work anymore. The last.fm pluging
> connects fine to last.fm  but nothing appears on last.fm.
> 
> I wonder if there are others with the same problem?
> 
> The problem has probably nothing to do with Amarok itself. On my main
> pc running latest version tumbleweed/kde 6.1.3 I'm using Amarok 3.0.81
> 
> On an other pc running OpenSUSE Leap 15.6 /kde 5.27.11 Amarok 2.9.71
> doesn't send the songs to last.fm too.
> 
> Spotify works fine.
> 
> Kind regards,
> Martin
> 
> --
> Martin Byttebier <martinbyttebier at gmx.com>
>