Bugzilla – Bug 17517
Home menu suddenly shows only 3 items every few hours
Last modified: 2011-10-03 10:01:26 UTC
After Release 7.6.1, some Squeezebox Radios that are connected only the MySqueezebox.com appear to revert to showing only 3 items on the Home menu: 1. Now Playing 2. My Music 3. Settings This problem appears to be happening much more frequently after this release. Other symptoms include: 1. Player name now "nil" 2. Unable to select Radio presets 3. After 3-4 hours, player reverts back to 3 item home menu even after it's OK. 4. For some Radios, power cycle is required to resolve. On others, it appears to straighten itself out. Above will happen if connectivity between Radio and MySqueezebox.com is lost. This appears to happen even though connection with internet is stable.
FYI: 3 items on home menu == no server
...and probably the same issue as 17518
These observations apply specifically to SbS, not SN. Something similar may be happening with SN but the implementation is different there. If a SlimProto connection has not been made by the time the Comet connection is made then attempts to subscribe to player-specific requests will fail. Once one request has failed then no other request in the same Comet request will be processed. The order of subscribe requests in the Comet request is random (based on hash keys). If the serverstatus subscription request does not succeed, because of a preceding error, then the Comet connection will timeout after 65s, be remade and the problem will self-heal. If the serverstatus subscription request does succeed but other (player-specific) subscription requests fail then the player can end up in a bad state which will not fix itself automatically.
== Auto-comment from SVN commit #33267 to the slim repo by ayoung == == http://svn.slimdevices.com/slim?view=revision&revision=33267 == bug 17517: Home menu suddenly shows only 3 items every few hours SbS fix. Fail Comet connection if an attempt is made to subscribe to a request for a Client which is not available. The automatic Comet connection retry will give time for the Slimproto connection to be established, and the subscribe requests will be reissued on the new connection.
Is this the same as bug 17518?
*** This bug has been marked as a duplicate of bug 17518 ***