Bugzilla – Bug 12255
Factory reset offers update from SN to same version and shows "?"
Last modified: 2009-10-05 14:27:19 UTC
To reproduce: Have latest firmware. Factory reset. Setup wifi. The following screen appears: "The software for this remote is up to date. If you'd like to reinstall version ?, choose Begin Update" SN has the same version, and should be reporting a firmwareUpgrade value of 0 to not force update. Also, the URL from SN contains the version so parsing the version should work and not show a "?". After doing the update (there is no choice to skip), things are fine.
Oh, and the string there probably shouldn't say "remote".
Further: if you have a local server running on the same network, with the same version or older available, those servers also show up as valid firmware upgrade(ers)
I had a local server with the same latest version and did NOT see that, actually.
I never saw the ? show up, only my local servers
(In reply to comment #2) > Further: if you have a local server running on the same network, with the same > version or older available, those servers also show up as valid firmware > upgrade(ers) At r6057, I see the same thing. It shows the version number and forces an update to the same version that's running. With two SC 7.4 servers (Trunk and SQLite branch) running on the local network, after setting up wifi and a 'Connecting to mysqueezebox.com' screen, I get: Software Update Begin Update (7.4 r6057) - [SC7.4 MySQL] Begin Update (7.4 r6057) - [SC7.4 SQLite]
At r6084 now I see the behavior described by Andy in the original description. A "?" for the version and a forced update. There is _one_ way around the forced update - by rebooting. It remembers the wireless credentials, automatically connects to the wifi network and then begins the SN signup portion of the setup.
r6089. Just did another factory reset and in the setup I again see the screen described in comment #5, listing the server names and the firmware version numbers. I think the difference is that in comment #6 I had only one local SC server running. Now and in comment #5 I have two local servers running.
BTW, nobody has mentioned how this should be resolved... If the firmware is up to date during the initial setup, then this screen should never appear.
Reset priority before triage.
Matt, can you update this string to not refer to "this remote" UPDATE_BEGIN_REINSTALL EN The software for this remote is up to date. If you'd like to reinstall version %s, choose Begin Update.
(In reply to comment #10) > Matt, can you update this string to not refer to "this remote" > > UPDATE_BEGIN_REINSTALL > EN The software for this remote is up to date. If you'd like to > reinstall version %s, choose Begin Update. If we can tell that this is a controller, then we'd say "The software for this controller is up to date. If you'd like to reinstall [current version], choose Begin Update. Skip Update > Reinstall [version #] >" If we can't tell that this is a controller (maybe this is the only case we use?), we'd say "The software for this Squeezebox is up to date. If you'd like to reinstall [current version], choose Begin Update. Skip Update > Reinstall [version #] >"
strings added for comment #11 - r6800
Was this marked FIXED by accident or has it reverted to its previous behavior? With r7262 on Fab4, I'm being forced to reinstall the same firmware during setup. Repeatedly. With no way out. 1) I still see "If you'd like to reinstall version ?, choose Begin Update. 2) There's no way to skip the update. Please reopen.
Jim: there was an error on SN just now, it should be fixed now
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.