Closed
Bug 300872
Opened 19 years ago
Closed 19 years ago
1.0.4 software update does not identify 1.0.5 as (critical) update.
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: johansen, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 On 2005 July 15 Friday Firefox 1.0.5 is presented (and widely reported) as a critical security update. Yet, in 1.0.4, choosing Tools | Options | Advanced | Software Update | "Check Now" button reports "Firefox was not able to find any available updates." Reproducible: Always Steps to Reproduce: 1. From the menu bar choose Tools. 2. Choose Options. 3. Choose the Advanced panel. 4. Expand Software Update. 5. Choose Check Now button. Actual Results: See in dialog box, "Firefox was not able to find any available updates." Expected Results: Starting of download process for 1.0.5. Workaround: surf getfirefox.com; download/install 1.0.5.
Comment 1•19 years ago
|
||
The update system notification for a new update usually doesn't begin until a day or two after the initial release. (sry, getting sleepy...) -> INVALID?
| Reporter | ||
Comment 2•19 years ago
|
||
(In reply to comment #1) > The update system notification for a new update usually doesn't begin until a > day or two after the initial release. (sry, getting sleepy...) > > -> INVALID? If, in the fullness of time, someone finds 1.0.4 flags 1.0.5 and starts the update, I'm happy to have 300872 INVALIDated. I cannot do the test, as, in the course of checking out conditions, I have already updated all my home net to 1. 0.5 and I don't want to roll back. BTW, 1.0.1 found and updated to 1.0.5 tonight, while another 1.0.4 afterward wouldn't and was updated "by hand." Cheers. --CKJ
Comment 3•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 I can`t update from 1.0.4 to 1.0.6 using the auto-update.
Comment 4•19 years ago
|
||
(In reply to comment #1) > The update system notification for a new update usually doesn't begin until a > day or two after the initial release. (sry, getting sleepy...) > > -> INVALID? Firefox 1.0.5 was released on 7/12/05. Chris tried to use auto-update on 7/15/05, so I'm assuming it should have been up by then. If I recall correctly, I updated from 1.0.4 to 1.0.5 on 7/14 myself, and Software Update didn't find 1.0.5 either. I did update to 1.0.5 by hand. Firefox 1.0.6 was released on 7/19, and again I tried to update to that from 1.0.5 on 7/20. Again, Software Update didn't find 1.0.5, and I updated by hand. Now, that time the update URL might not have reflected the change yet. In both cases, I had already known about the new version from checking the Mozilla.org homepage. Prior to updating from 1.0.4 to 1.0.5, the updates would be found on the same day that Mozilla.org posted that they were available. I checked about:config, and I have the following settings: app.update.autoUpdateEnabled - true app.update.enabled - true app.update.interval - 86400000 (not sure if this setting matters or not) app.update.url - http://update.mozilla.org/update/firefox/en-US.rdf I remember when 1.0 RC1 came out that we had to change the last setting for Software Update to find it, and then had to change it back to the above for it to find 1.0 final. Has the update URL changed again?
Comment 5•19 years ago
|
||
AFAIK the update system was never invoked for firefox 1.0.5 because of the issues it had, the app update system wasn't switched on until a few days after the release of firefox 1.0.6. Which would make this invalid. If you reinstall firefox 1.0.4 does it prompt you about the avaliable update to 1.0.6 (you need to wait at least 24 hours)
Updated•19 years ago
|
Version: unspecified → 1.0 Branch
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•