Bug 10403 - SqueezePlay can not switch SqueezeBox to SqueezeNetwork or itself to SN (for remote player)
: SqueezePlay can not switch SqueezeBox to SqueezeNetwork or itself to SN (for ...
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: unspecified
: PC Ubuntu Linux
: P1 normal (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on: 12207
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-19 21:05 UTC by Mikael Nyberg
Modified: 2009-10-05 14:37 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments
gdb of conection attempt (15.95 KB, application/octet-stream)
2008-12-19 21:31 UTC, Mikael Nyberg
Details
server log during connection attempt (5.40 KB, application/octet-stream)
2008-12-19 21:33 UTC, Mikael Nyberg
Details
another server log different log settings (4.84 KB, application/octet-stream)
2008-12-19 21:42 UTC, Mikael Nyberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikael Nyberg 2008-12-19 21:05:34 UTC
SqueezePlay can not switch SqueezeBox to SqueezeNetwork or itself to SN.

Sorry for the messy bug I have hunch that the 2 problems are related.

1.
Sp can not switch any of hardware players to SqueezeNetwork. that is one SB3 and 0ne SBR, You get the "problem connecting" screen.

2.
When you want to connect squeezeplays own player to SN there is no menu item "squeezenetwork" just my server or "other server".
If you punch in SN's ip address as "other server" SP gets conection problems with everything including my own server.
Comment 1 Mikael Nyberg 2008-12-19 21:31:55 UTC
Created attachment 4481 [details]
gdb of conection attempt
Comment 2 Mikael Nyberg 2008-12-19 21:33:42 UTC
Created attachment 4482 [details]
server log during connection attempt

server log during connection attempt.
My log settings is probably way off , please advice.
Comment 3 Mikael Nyberg 2008-12-19 21:42:17 UTC
Created attachment 4483 [details]
another server log different log settings

another server log different log settings.
Comment 4 James Richardson 2008-12-22 11:19:49 UTC
Mikael: SqueezeNetwork does not know about SqueezePlay yet, this will be a function very soon.

Ben, please re-target as needed.
Comment 5 Wadzinski Tom 2009-07-31 14:33:18 UTC
fixed for remote ip3k players.

For remote SP players, bug 12207 needs fixing.
Comment 6 Wadzinski Tom 2009-09-02 20:48:27 UTC
This is blocked by a P2 bug (12207), so I don't see it getting done, unless the 
priority of the P2 bug is changed.
Comment 7 Pat Ransil 2009-09-15 19:15:39 UTC
12207 is now a P1 so when that gets fixed, retest.
Comment 8 Wadzinski Tom 2009-09-22 08:33:11 UTC
I just need to confirm that this is working now that 12207 is complete.
Comment 9 SVN Bot 2009-09-24 08:35:48 UTC
 == Auto-comment from SVN commit #7730 to the jive repo by tom ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7730 ==

Fixed Bug: 13907
Fixed Bug: 14216
Fixed Bug: 10403
Description:
SlimMenus:
- added _player:setServerRefreshInProgress(true) for cases where reconnected to same server
- increased log level for unusual cases to info
- bump on "Switch to SN" if SN unavailable
- menus were not being loaded for jive if player not connected to server on restart.
Player:
- Handle cases where uuid should be interpreted as nil
- do serverRefreshInProgress check to properly handle a reconnection to same server

SlimDiscovery:
- handle 000000... uuid case

PlaybackMeta:
- use saved serverInit data even when starting up with SN
(Reviewed by rt)
Comment 10 James Richardson 2009-10-05 14:37:06 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.