Bug 12992 - Baby connected to SN loses ability to switch services
: Baby connected to SN loses ability to switch services
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: Networking
: Include FW version in comment
: Macintosh Other
: P1 major (vote)
: CXR
Assigned To: Wadzinski Tom
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-22 18:18 UTC by Spies Steven
Modified: 2009-10-06 09:22 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Spies Steven 2009-07-22 18:18:37 UTC
I have my Baby connected to SN without a local server running and I have not selected a local server since I did a factory reset.

Steps to reproduce:
1 Factory Reset Baby and connect to SN on a network that does not have a local SC.
2 After entering SN credentials play some songs from a premium service without connecting to a local server, I choose Pandora.
3 Let a few songs play and then navigate to the home menu and choose a different service, I choose Rhapsody.

Notice you are now presented with a Libraries screen and the only choice is Remote Library.  Also notice that Pandora will continue to play and that the now playing screen will continue to update.  The Diagnostics screen will also show that Baby is still on the network and everything appear to be fine.

Power cycling Baby seems to correct the issue for a while.
Comment 1 Richard Titmuss 2009-07-27 01:09:52 UTC
Reset priority before triage.
Comment 2 Wadzinski Tom 2009-07-27 21:54:57 UTC
This is mostly fixed as of r6805. However, there is still a timeout that occurs which I think should not be occurring, so after 70 seconds you will see a reconnecting popup, but the reconnection should occur successfully.
Comment 3 Wadzinski Tom 2009-07-29 07:01:27 UTC
Remaining issue in comment #2 is now in bug 13094
Comment 4 James Richardson 2009-10-06 09:22:26 UTC
This bug has been fixed in the latest release of MySqueezebox.com (formally
known as SqueezeNetwork)!

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