Hello
I recently installed Amarok 2.3.0.Last.fm scrobbling doesn't work.I try to log in from the app and it appears the message "No running KWallet found.Would you like Amarok to save your lastfm credentials in plaintext?".I click yes but it doesnt scrobble.I go again in prefereces to see lastfm and I'm not logged.
I would like to scrobbling.What is the solution ? Thanks

It definitely works her in Amarok 2.3-git, I will ask a developer.

I fixed it.Somebody told me in irc. I disabled kwallet in amarok.krc file with a text editor.I writed ignorewallet=yes if i remember well.Now it works

P.D: I wonder , is it necesary the feature of KWallet in Amarok.It is a big source of problems

inmortus wrote:P.D: I wonder , is it necesary the feature of KWallet in Amarok.It is a big source of problems

Yeah, we are aware of these issues with KWallet.

It's not quite easy to handle it correctly, especially not if this system is optional. But I think we have a fix for this in the pipeline.

is the solution supposed to be adding the line "ignorewallet=yes" to amarokrc in /home/username/.kde/share/config?

i have tried this and scrobbling still does not work

i am running amarok 2.3.0 using KDE 4.4.1 on ubuntu


EDIT: so ive manually edited the amarokrc file from a backup of that file from 2.2.2. i inserted the entire part for last.fm (username, pw, ignorewallet=yes, etc) and now scrobbling works. amarok doesnt give confirmation that it scrobbled, but they do appear on last.fm.

No, you gotta add exactly

Code: Select all

ignoreWallet=yes

to ~/.kde/share/config/amarokrc

Just managed to make it work with 2.3.1 with all the info scattered on the thread. If you run into it, Go to [Service_LastFm], then add "username=..." , "password=..." and "ignoreWallet=true"

It then asked about KWallet on start up but left me alone afterwards.

Where can I find this file on windows? I am using 2.3-Git

it can be found here; C:\Users\<username>\AppData\Roaming\.kde\share\config\
works well for me

Nice it works now. Thanks alot

I should add that we have solved this bug for real now in Amarok 2.3.2 (coming soon).

It was a rather silly bug in the end, and I figured it out after staring a few minutes at the code