Bugzilla – Bug 8696
controller connected to boom never leaves "updating fw" spinny after boom fw update
Last modified: 2008-09-10 16:47:05 UTC
Not sure that this will be relavent anywhere else so I won't log a bug unless someone deems it a valid issue. 0) Old boom was unplugged. 1) Downloaded latest nightly with new firmware 18 this morning. 2) Installed it with no issues. 3) New boom was plugged in and updated without an issue. 4) Plugged in old boom and it updated without an issue. 5) However, the controller - which was looking at the old boom as the current player - went into a spinning wheel stating that it was updating the "squeezebox firmware". It never stopped. I had to power it off after about 10 minutes. Powered it back on and it worked fine. The controller is still at r2551 from June 11 so it must have been showing that the old boom was updating and didn't notice that it had finished for some reason.
I saw this with an sb3 last night, so it doesn't appear to be boom specific. It was still the boom branch, however.
see also bug 8726, left open since it's not a secured report like this one.
That bug is closed. Ben: Can you reproduce this? Do you need some help?
I just reproduced this. Retarget for 7.2 :( I'll try to figure out what's going on with this tomorrow. Methinks a playerstatus or serverstatus message is not sending the proper data to allow the SBC to exit the spinny.
Bah...I just went through the steps to reproduce this 10 successive tries today and I can't reproduce it. Clearly, as I saw yesterday, it happens once in a while...my hunch is that either playerstatus or serverstatus messages quit being received or still contain the player_is_upgrading flag, but the cause is unclear and without reproducing it I can't see how I'll get anywhere with this... retarget for 7.3 I guess. Much as this is ugly, for the most part I believe it will not happen, and when it does can be worked around (power cycling the controller, for example)