Closed Bug 417802 Opened 17 years ago Closed 16 years ago

Firefox downdate to an older version when I use others admin accounts

Categories

(Toolkit :: Application Update, defect)

1.8 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 485624

People

(Reporter: riccardo.boldrini, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.8.1.10) Gecko/20071115 Firefox/2.0.0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.8.1.10) Gecko/20071115 Firefox/2.0.0.12 I have 2 admin accounts on win xp sp2 updated and I use one of them often and the other sometimes. In the first FF 2.0.0.11 updates automatically to new version 2.0.0.12. In the second account when I use FF is updated to version 2.0.0.12 but it download the version 2.0.0.10 and it install it. After the downdate it detect that there is a new version and it download the new version for a reinstall. If I make a reinstall in the first account it downdate and the cicle restart. I think it is a bug. Reproducible: Always Steps to Reproduce: 1. Two accounts admin on win xp sp2 (I think that happens in windows vista but I have no tried). Automatic update activated 2. in account 1 it make the update to new version 3. in account 2 it make the downdate to older version and wont make update to new. 4. with the new version reinstalled, in account 1 it download the old version and it re-reinstall the new version. Actual Results: I have deactivated automatic update Expected Results: that it not download older versions from your website, that it recognize older version and that it no instal it. boh... It's the normal version of FF. I can't understand how this is possible... I can send a screenshot where there is the update window (that download the 2.0.0.10) near the info window whit printed the version (2.0.0.12)
Version: unspecified → 2.0 Branch
Product: Firefox → Toolkit
Looks like a dupe of bug 353804
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.