311656 - Fx Beta 1 auto-update to Beta 2 does not seem to work under Windows

Status: RESOLVED DUPLICATE of bug 309784

(Toolkit :: Application Update, defect)

Description

[Ivo Goncalves]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

When Fx Beta 2 (Deer Park) was released one day and some hours ago (according to
slashdot, where I read the announcement), I read we should turn auto-update on
for testing purposes--I had mine off since the Fx 1.0.x series. I turned it on
immediately, but until now, I have mostly remained online and I have got no
confirmation of a new version, or if it should download new version, etc. I
don't know if this might have been because I had auto updates turned off before
the new release came out. I tried to search for a similar bug and I have found
nothing yet, so I guess I am either one of the few, or everyone is waiting if
the auto update to notify of something some other time.

Reproducible: Always

Steps to Reproduce:
1.Turn auto update on
2.Wait one day and a half
Actual Results:  
No confirmation of a new version.

Expected Results:  
Prompt me to download the new version in order to update, I guess. I can
download and update manually as I used to do on the 1.0.x series, so I rate this
issue a "minor loss".

Comment 1

[Jo Hermans]

To avoid server-overload, auto-updates were not immediately enabled, but they
are now (<http://weblogs.mozillazine.org/chase/archives/009045.html>). But it
can still take some time before FF will try to check the website. You can expect
that can auto-update in the next few days. Manually updating works though.

Comment 2

[Ivo Goncalves]

Oh, I know manual update would work. My intention in using the Beta was to help
with testing, and same applies for the auto update now. I however decided now to
use the Help > Check for Updates option. The results weren't very good. It found
the update, and tried to extract a partial update around 700 kb. Fx told me it
needed to be restarted to apply the patch. I allowed it, but then it told me the
partial update failed and it needed to use the full update. So it downloaded a
second file this time 6 mb big. Ok, shame the partial update failed, but I can
live with that. It prompted me to restart again, and this time it seems to have
worked (it even directed me to the mozilla site saying congratulations et al).
However, all my extensions, which worked with Beta 1, do not work anymore with
Beta 2. I am shocked. I could understand that my old extensions from the 1.0.x
series wouldn't work on 1.5b1 (major re-design I assumed), but after getting new
extensions for 1.5b1 and seeing they don't work anymore on b2 is quite
disturbing. It makes it impossible for users to keep their extensions working,
and for developers to track what the hell to change now on their extensions, or
even to keep them backwards-compatible. Fx is becoming a extension nightmare!

Enough ranting. The original bug remains really. I got no update notification
and forcing to check for update got Fx to download a partial update that
wouldn't work; it required a full update download, and I think it's important to
report that. Not to mention the damn extension issue...

Comment 3

[Dave Townsend [:mossop]]

The lack of an automatic update check was known about.

Comment 4

[Dave Townsend [:mossop]]

*** This bug has been marked as a duplicate of 309784 ***