Bugzilla – Bug 13529
Confusion starting network test from Controller
Last modified: 2011-01-14 12:11:35 UTC
Initiating a network test with the Controller while the Controller is controlling a Boom causes the Boom to become unresponsive until I use the left arrow button on the Boom itself to escape the test. Shouldn't it be possible to stop the test from the Controller since it was started there? It would also be nice to have some explanation of what it going to to happen BEFORE the Network Test happens, along with instructions on how to stop the test. I went into the Network test menu by accident and it was very scary when my Boom became unresponsive and I couldn't figure out how to stop it (see the linked forum thread). Controller r7158 Server 7.4 - r28225
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
On the controller if you exit the network test screen it should stop the test to the player. I've not got a controller to hand, but this works from for me from an emulation of the controller. Assuming it works for you, it probably just needs something added to the description string to say "left to stop" ?
Adrian, it does not work for me. My Boom is now stuck in network testing mode and I cannot get it out of it. I tried shutting down the server, disconnecting the Boom from the power, and of course presseing the "back arrow button", etc. Somehow the network testing state always survives. In the meantime, till this is fixed, how do I get out of this? My Boom is currently completely useless. I guess there must be some way to fix it while the server is stopped.
Network test is actually a state on the server rather than either the player or the controller. If you restart the server application then it will definately clear the network test state. It should also happen if you "power off" the player from the server web interface. I think you say you have restarted the server but it sounds like it has not actually restarted.
Actually, I have restarted the server SEVERAL times, but it didn't help. What helped, was to set NetTest in /var/lib/squeezeboxserver/prefs/plugin/state.prefs from "enabled" to "disabled" and restart the server. But then again, when setting it back to "enabled", the old behaviour was back and the network test was endlessly looping. Then I realized that the Controller started to feel sluggished and turned the Controller (!) off. This immediately cured the problem. So, while the Controller perfectly left the network test screen and - albeit sluggishly - allowed me to browse the menu structure it was somehow still stuck in network testing. So, restarting the Controller cured the problem. Make of that, want you want, I now know not to use the network test plugin anymore and most likely will leave it disabled.
BTW: Thanks for the quick response on a Saturday evening.