353291 - Firefox updates to 1.5.0.7 multiple times

Status: RESOLVED INCOMPLETE

(Toolkit :: Application Update, defect)

Description

[Alek Kowalczyk]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

Previous version was 1.5.0.6. User Agent string shows it is successfully updated to 1.5.0.7 already.
Sometimes after Firefox starts I get window that new version (1.5.0.7) is available. My Firefox already "updated" to 1.5.0.7 three times :) .

May 





Reproducible: Sometimes

Steps to Reproduce:
1. Open Firefox

Actual Results:  
Update dialog shows possibility to update to 1.5.0.7. "Update" is performed successfully after confirmation.

Expected Results:  
Firefox should just open, as it is already 1.5.0.7

May it be a duplicate of Bug#314684?

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

It's possible for everything except firefox.exe to get updated, usually when another application is holding a lock on the executable, or firefox does not exit completely. Then the UI will say 1.5.0.7 but the exe is 1.5.0.6, and the latter is used for the version when requesting updates.

Please look at the properties of firefox.exe, in the Version tab, at the fields in the Item List. You should have "1.8.0.7: 2006090918" for "File Version".

You may also get some information from C:\Program Files\Mozilla Firefox\updates\last-update.log, and updates\0\update.log (if it exists). Attaching those to this bug may be useful.

Comment 2

[cameron davidson]

This might be the same as I am seeing.
Was 1.5.0.6, upgraded to 1.5.0.7 and the following day the "about" page said it was 1.5.0.2!  And it did an upgrade again.
After this happening twice, I uninstalled firefox (but kept my profile) and installed from a fresh download of en-US.
I disabled auto updates completely and when I came in the next day, there was 1.5.0.2 back again. The version of Firefox.exe confirms this.

I wonder if there is some system restore activity going on.

I have archived copies of the "program files" tree and will check for any overwriting.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

System Restore can cause problems, see bug 351216.

Comment 4

[cameron davidson]

I had not actually used system restore - I was confusing myself there - thinking about some automated process that might run while I wasn't looking.
A bit more info.
Firefox was running overnight, and the replacement to 1.5.0.2 occurred at 05:33. There is a windows prefetch entry for "Firefox Setup 1.5.0.2.exe" at that time, as well as one for 1.5.0.7 when I later came in and performed the manual update.
Also in D:/temp/sys/ff_temp/...   (from memory) were dlls for firefox 1.5.0.2. Dates/times were also tuesday at 05:33
The ff 1.5.0.7 versions of these files were under D:/tmp/..., which is actually a different folder on my system. Now, D:/temp/sys is the TEMP enviroment variable for the system, not for me.

So it looks exactly as if the 1.5.0.2 setup program was run behind my back.
There was no record of 1.5.0.2 in the "update history" box (tools->options->advanced) - only the 1.5.0.7. .
There is no copy of the 1.5.0.2 setup executable that I can find anywhere on my system or attached network drives.
Last night FF was not running and there was no change.

Even more curiously, I borrowed a laptop two days ago - one that I had never previously used - and noticed that even though FF was set for fully auto-updates, it only had 1.5.0.2.
After getting admin rights, I upgraded to 1.5.0.7, shut down overnight, and the next day is was on 1.5.0.2 again. The "show update" history said 1.5.0.7 was updated at 13:36, but the firefox.exe is version 1.5.0.2 and create time is Oct 15-2005, modified time is Tuesday at 14:35, one hour after I upgraded to 1.5.0.7.  I just updated it to 1.5.0.7 again, and the previous history has been wiped out.

This may be irrelevant, but I notice registry entries on both machines to HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\ShellNoRoam\MUICache
referring to "D:\\TEMP\\sys\\Firefox setup 1.5.0.2.exe"="Firefox"
(and the appropriate temp dir on the other machine)
There is a duplicate entry under the S-1-5-18 sid (the "local system" user)

Comment 5

[cameron davidson]

I think I may have found the cause of my problems and it might have wider implications.
It seems our corporate IT support implemented automatic upgrades to Firefox, but after 1.5.0.2 they have forgotten about it.
When you do "properties-> version" on firefox.exe there are two different file versions. One is on the main page itself, and a different value is visible when you select "file version" under the "item name" list.
item : 1.5.0.2: 2006030804     shows  1.8.20060.30804 on the top line
but
item : 1.5.0.7: 2006090918     shows  1.8.20060.25382  on the top line

So if scripts use the top "file version" then 1.5.0.2 looks newer, and this old script that has been forgotten about suddenly springs to life.

Comment 6

[Hermann Schwab]

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1) Gecko/20060920 BonEcho/2.0

I'm on Win98 (german) and use zipped builds, looking at the properties of 1.5.0.7 gives me:
file version:      1.8.0.7: 2006082915
product version:   1.5.0.7

Comment 7

[cameron davidson]

Attachment: illustration of version mismatch

oops, sorry.. The file version under "item name" should read 1.8... in both cases.
But my point is that there are two different "file versions" and they compare inconsistently.
I have attached an image illustrating what I am referring to. Ignoring the missing  ".0.7", the trailing 5 digit number on the top is lower for 1.5.0.7 than for 1.5.0.2. For 1.5.0.2, the top trailing fragment was created by the date

Comment 8

[Carsten Book [:Tomcat]]

cameron, do you still have this update problem also from Firefox 2.0.0.3 to Firefox 2.0.0.4 ?

Comment 9

[Samuel Sidler (old account; do not CC)]

This is likely a dupe of the other issues we've had related to receiving the same update twice. Closing it as INCOMPLETE due to lack of information.

Cameron, if you can still reproduce using Firefox 2.0.0.x (since 1.5.0.x is no longer supported), please comment here.