User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Running Firefox 0.9.1 on Win2k, Software Update is not detecting that version 0.9.2 is available for download, nor does it find the security update for bug 250180. In Tools | Options | Advanced | Software Update, the option to check for Firefox updates is enabled, but no notification has yet been received. Tried the Check Now button, but Firefox Update ran and reported "No Updates Found." Reproducible: Always Steps to Reproduce: 1. Installed Firefox 0.9.1 on Windows 2000 and imported IE settings. No out-of-box config options were changed. 2. Clicked on Tools | Options | Advanced | Software Update | Check Now. Actual Results: Firefox Update ran and reported "no updates found" when there was a patch and a new version available from Mozilla's website. Expected Results: When clicking Check Now, it should have detected that a new version had been pubished and presented options to download and install. Also, since the option to periodically check for new versions was enabled, it should have popped-up a notification that a patch was available (without having to click Check Now). Security concern: many users rely on the Security Update feature to let them know about newly discovered vulnerabilities. If available updates are not detected, users may not learn of them and thus remain vulnerable.
Yes, it's a known problem. The version for 0.9.1 and 0.9.2 was set to "0.9" to avoid breaking all the extensions. Initially the updater was told that 0.9.1 was the latest version, but unfortunately that meant telling users of 0.9.1 to update to 0.9.1 - same thing would happen with 0.9.2. So the choice was between telling everyone to update even if they had already, and not telling anyone to update. That's all been fixed now, so as of the next version, it will be possible to release an update without breaking things, and the updates will work. Not quite sure how to deal with this report - this bug is a result of the workaround for other problems. Now that the other problems are fixed, the workaround won't be used again and this issue won't arise. I guess this is a dupe of bug 249251, or maybe bug 245953, which are about the underlying issues. *** This bug has been marked as a duplicate of 249251 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.