GNOME Bugzilla – Bug 627011
Change Last.fm user account
Last modified: 2020-03-17 08:46:47 UTC
it is impossible to change username and password if entered wrong no ui for enter a new user name or password this is a showstopper for using last.fm if entered wrong in first try
I'm not sure I understand what you mean : Banshee only asks for your Last.fm username, not for your password. It then open a page in your web browser, on the last.fm website, where you have to authorize Banshee to access your account. Could you describe exactly your problem, with detailled steps to reproduce it ? Screenshots might also help.
Created attachment 167985 [details] Account Name Screenshot 1, Last.fm Account name
Created attachment 167987 [details] unable to change accaunt name No way to change Account name
sorry this but system is a little confusing think i have made 3 replays Description of use case screenshot1 i enter my account name "notmyaccount" and press "log in to last.fm" then in screenshot2 i have no way to change "notmyaccount" to an valid useraccount name the only workaround is to create an account on last.fm with the bogus "notmyaccount" user name. but if i just have misspeld or typed wrong my account name i have no way to figure out what that was hope it is clear now
Ok, got it, thanks ! Another work-around is to use goncf-editor to go and find the following preference and unset it : /apps/banshee-1/plugins/lastfm/username The problem the "Try again" button just opens another browser page, and the "Finish logging in" doesn't work : as it is the wrong username, we get a TokenNotAuthorized error. We should probably got back to the first step in that case.
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the responsibility for active development again. See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.