Bug 13509 - Invalid login or password message
: Invalid login or password message
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: SqueezeNetwork
: unspecified
: PC Windows XP
: P1 normal (vote)
: 7.4.0
Assigned To: Weldon Matt
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-19 17:13 UTC by Mickey Gee
Modified: 2009-10-05 14:34 UTC (History)
3 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2009-08-19 17:13:03 UTC
When upgrading to 7.4 r7115 firmware, user sees "invalid login or password" message because user account on test.sn.com does not have correct name or password. Reported in forums, so not sure how to reproduce.

Message needs to be clearer on steps for user to resolve issue.
Comment 1 James Richardson 2009-08-20 10:37:54 UTC
The root of the cause is not important for this bug.  The issue is the message is not very clear as to what the customer needs to do to solve the issue.
Comment 2 Weldon Matt 2009-08-20 12:59:15 UTC
The cause is actually semi-important in terms of explaining to the user wht the heck is going on :-).

Can someone point to the relevant forum thread, or give any more info?  this isn't enough information for me to do anything about this...
Comment 4 Weldon Matt 2009-08-26 16:10:14 UTC
He was using the wrong firmware (7.4 instead of 7.3.x).  Check the thread, issue was resolved.
Comment 5 James Richardson 2009-10-05 14:34:25 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.