Bugzilla – Bug 12068
"Update Software" error message is incorrect/not helpful
Last modified: 2009-10-05 14:30:09 UTC
In "My Music," Squeezecenter servers appear in the list that I've previously connected to, even if they are currently available (in this case the computer is powered off). The error I get is "Update Software;" with a message that "[servername] needs to be updated to a newer version of the Squeezebox software." This is a totally incorrect message. My SC version is fine, it's just not running. The case where the [servername] is unavailable (server is turned off, I switched networks, I turned off the computer, etc) is going to be WAY more common (I would think) than the case where SC is too old to work properly with the fab4. We need more intelligent error messaging here. Deep thought: this bug is making we wonder if we're being "too clever by half" by caching and displaying previously-connected SC instances, even when we can't detect them.
To clarify: the bug occurs when I click on the name of an SC instance that is currently not available (computer is turned off, SC is turned off, or SC/computer is no longer on the same network). The "Update Software" message is shown after I press the name of the SC instance.
Reset priority before triage.
There is no SLT work here.
Happens due to version check before version info availble. Discovery now has version info, but this might not be tied in yet. Tom, confirm.
Version info comes in discovery now, so this message should no longer falsely appear.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.