Bug 15363 - Selecting mysqueezebox.com gives no way out, back to local server
: Selecting mysqueezebox.com gives no way out, back to local server
Status: RESOLVED DUPLICATE of bug 14264
Product: MySqueezebox.com
Classification: Unclassified
Component: Signon
: Prod
: Macintosh MacOS X 10.4
: -- normal (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-22 16:15 UTC by Daniel Barrett
Modified: 2010-01-11 16:39 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Barrett 2009-12-22 16:15:02 UTC
1. Begin with a brand new Squeezebox Classic V3 (and possibly other models) and server 7.4.1.

2. Complete the setup process. (I used wireless networking with WPA2, and connected to my home music server.)

3. Out of curiosity, locate and select mysqueezebox.com from the menu.

4. It prompts for a username/email address. Change your mind and try to back out.  Surprise, you can't!  (This is a misfeature, but not the critical error.) There is no way to go back to your home music server.

5. Looking for a way out, you scroll down to Help and select it.

6. Read the help message.  When you're done, notice there is NO WAY to exit help mode.  The up/down arrows scroll through the help message, but the left and right arrows do nothing. You can't leave. (This is also a bug, but not the critical error.)

7. In frustration, unplug and replug the squeezebox.  It boots up showing "Now Playing: Nothing". And no other buttons on the remote have any effect. You are stuck. (This is the critical error.)

No way out except to reset the squeezebox ("+" key and power on).
Comment 1 Michael Herger 2009-12-23 00:47:15 UTC
Press & hold left to get out in to the settings menu.

Just a workaround, not a solution. Thanks for the report!
Comment 2 Chris Owens 2010-01-04 09:35:16 UTC
This is a duplicate.  Chris to find the other bug and set it to duplicate.
Comment 3 Chris Owens 2010-01-11 16:39:01 UTC

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