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 373513 - lastfm plugin fails to re-initialize after repeated submission attempts
lastfm plugin fails to re-initialize after repeated submission attempts
Status: RESOLVED DUPLICATE of bug 499745
Product: rhythmbox
Classification: Other
Component: Plugins (other)
0.9.6
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-10 19:33 UTC by Kirk Bridger
Modified: 2008-08-13 00:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kirk Bridger 2006-11-10 19:33:14 UTC
Please describe the problem:
When setting up the lastfm plugin, I mistyped my username.  However the plugin reported a successful login.  After playing several songs I checked the plugin status and it reports the following error under the Status field:

Track submission failed too many times.

I have corrected the username and confirmed that the password works as typed to login to lastfm's website.  I have tried disabling then re-enabling the plugin.  I have tried restarting Rhythmbox.  However the plugin still reports this error and track submission is not working.

Steps to reproduce:
I am unsure if it is repeatable, as I cannot return to the no-failure state.


Actual results:


Expected results:
The plugin should allow a means of forcing a submission with the updated credentials, or do so silently after a change is made to the credentials.

Does this happen every time?
I am unable to clear this error and use the plugin.

Other information:
Comment 1 Jonathan Matthew 2008-08-13 00:37:37 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 499745 ***