After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 601309 - Improve the Last.fm authentication experience
Improve the Last.fm authentication experience
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Last.fm
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
: 603625 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-11-09 21:18 UTC by Bertrand Lorentz
Modified: 2010-05-22 09:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bertrand Lorentz 2009-11-09 21:18:38 UTC
After the move to the Last.fm 2.0 API (see bug #541227), the authentication process is quite different and some better UI or additional guidance would be nice.

You now need to authorize Banshee to access your Last.fm account. In order to do that you have to :
  1/ Go to Tools > Last.fm > Configure...
  2/ Click on "Authorize for Last.fm". This will open a page in your web
browser
  3/ In that page, log into you Last.fm account (if not already logged in) and  grant access to Banshee
  4/ Go back to banshee and click on "Save and Log In"
Comment 1 Alexander Kojevnikov 2010-01-29 23:39:05 UTC
*** Bug 603625 has been marked as a duplicate of this bug. ***
Comment 2 Jeffrey Finkelstein 2010-01-31 06:17:15 UTC
I did not realize that even after clicking the "Authorize..." button, and granting Banshee access on the Last.fm page, I still had to RETURN to Banshee and click on the small button with the "Refresh" symbol on it before Banshee would start reporting my songs. I think this is a pretty serious problem; there should at least be some clear directions on the Last.fm Source Preferences page.
Comment 3 Will Thompson 2010-02-15 11:35:05 UTC
Furthermore, there was no indication in the UI that I now had to authenticate: I happened to notice

  [Warn  11:28:03.734] Audioscrobbler sign-on failed - Last.fm username is invalid or Banshee is not authorised to access you account.

in the debug output (which has a typo: s/you/your/). I'd expect an infobar or something telling me that my songs are silently not being scrobbled.
Comment 4 Łukasz Jernaś 2010-03-28 20:25:15 UTC
In 1.5.6 the correct path is Edit->Preferences->Sources->[select the Last.fm source]->Authorize->[accept on last.fm page]->click "Refresh button" in Banshee.

The refresh step is kind of fail IMHO, it doesn't work if you had authorized Banshee, forgot to click it, and quit Banshee. On the next run you have to click authorize again, even though it is on the accepted list...
Comment 5 Bertrand Lorentz 2010-05-22 09:43:46 UTC
I believe this has been fixed by Aaron in the following commit :

commit 04343bf984e86c92b1768e72229a574faa9fc5a7
Author: Aaron Bockover <abockover@novell.com>
Date:   Mon May 3 22:19:06 2010 -0400

    [LastFm] Improved authentication experience
    
    Overhauled the workflow for logging in and authorizing Banshee to use
    Last.fm. The phases should be more clear now, and it is possible to log
    out and change accounts.
    
    Also show the AudioScrobbler enable/disable check box in the preferences
    dialog under the Last.fm page.

@Łukasz :
What was the "refresh" step in now clearer, but it still has to be there, as it is required by the Last.fm authentication process : Banshee has to do something after you've approved it in your Last.fm page.


This fix should be available in the 1.6.1 and 1.7.0 releases.