Bug 10156 - trouble moving players from SC - SN and back using Controller
: trouble moving players from SC - SN and back using Controller
Status: RESOLVED WORKSFORME
Product: SB Controller
Classification: Unclassified
Component: SB Server
: unspecified
: PC Windows XP
: P2 major (vote)
: 7.3
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-26 14:02 UTC by Ross Levine
Modified: 2008-12-09 13:51 UTC (History)
5 users (show)

See Also:
Category: ---


Attachments
log (8.07 KB, text/plain)
2008-11-26 14:03 UTC, Ross Levine
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Levine 2008-11-26 14:02:34 UTC
Both SqueezePlay and Controller 7.3 r3437 show this, when trying to switch the source of a player I sometimes can't choose one of the options, it bumps and refuses to allow choosing a source, in this case SN. 

Also sometimes it allows me to choose SN, the player moves to SN, and the Controller indicates a failure. See bug 10120, comment #14.
Comment 1 Ross Levine 2008-11-26 14:03:23 UTC
Created attachment 4353 [details]
log
Comment 2 Ben Klaas 2008-11-26 14:30:41 UTC
log doesn't show anything, but this is what to investigate--

line 162 of ChooseMusicSourceApplet.lua:
if server and currentPlayer and currentPlayer:canConnectToServer() then

one or more of these items is returning false when it (presumably) should not, which results in an item with the "bump" behavior.

...not the first time this bug has appeared.
Comment 3 Ross Levine 2008-11-26 15:27:51 UTC
The test.SN hacked redirect doesn't seem to be working properly; MWise can you please look into this? James and I are seeing players sometimes going to production SN instead of test, while connected to this network. 
Comment 4 Ross Levine 2008-11-26 16:28:48 UTC
I can't login to this base station to see whats going on. Steven, please take a look on Monday and see if anything is out of the ordinary. MWise suggests concerns with the IP and netmask. 
Comment 5 Matt Wise 2008-12-09 13:46:07 UTC
We determined that this was a bug in the firmware right -- not an issue with the wireless router? 
Comment 6 Ross Levine 2008-12-09 13:51:35 UTC
I can't reproduce this any more, not since the release of Falco.