Bugzilla – Bug 15806
Unable to connect to music library or music service if controlled player is powered OFF
Last modified: 2011-01-14 09:53:43 UTC
Using a Controller to control a Transporter, I noticed with today's firmware and Squeezebox Server that any attempt to browse my local music library, view radio stations, or select a music service would attempt to connect with my Squeezebox Server. Attempts and any retries to connect with my music library would fail. I realized that my Transporter had no AC power connected to it. Once I applied power and the Transporter booted up, I could browse my music library and all other activities as I expected. In previous versions of firmware, I could browse any item on the Controller menu without requiring a player turned on. Being unable to browse unless the player turned on is a functional change from 7.4. Jive firmware r8597, SbServer r30277
This is probably a SqueezePlay-player interaction, so please recategorize as appropriate. Possibly also due to changes created by bug 15633
This is very likely connected to bug 15633 although, for a remote player, I cannot think of what specific change could have affected this behaviour. I would always have expected to be impossible to browse My Music unless the player was connected.
Mickey, can you confirm how the controller got into this state. My guess is that it was connected to (controlling) the Transporter which was then switched off (AC power removed). Some time later, you tried to use the controller and found that you could not browse into some menus. How sure are you that this worked with 7.4?
I can confirm this report with Jive 7.5 r8597 against both SbS 7.4.2 and SbS 7.5 r30281 I just downgraded to Jive 7.4.1 r7915 and ran it against SbS 7.4.2. I see the same behaviour. Therefore, I believe that this is not a change from 7.4 to 7.5.
Mickey, please describe exactly what functionality you expect to work here. To the best of my knowledge, it has never been possible to browse music sources (local library, or services) other than in the context of a current (connected) player.
Haven't noticed this issue for awhile. Will reopen if I do.