Closed
Bug 374800
Opened 18 years ago
Closed 18 years ago
firefox upgrade 2.0.0.3 tries to automatically install as regular user (and fails of course)
Categories
(Firefox :: Installer, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 374900
People
(Reporter: cwi8q0l02, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.4; en-VS; rv:2.8.1) Gecko/20071110 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.4; en-VS; rv:2.8.1) Gecko/20071110 Firefox/3.0
The firefox 2.0.0.3 upgrade is trying to install when I logged in as a regular ("limited") user. Naturally this fails.
When I log out, and log in as an admin, then it doesn't seem to have even downloaded the upgrade.
So, it looks as though it downloaded it to somewhere specific to the limited user -- that seems pretty wrong, and doomed to failure?
Reproducible: Always
Steps to Reproduce:
I don't know what to put here. See my description above.
Actual Results:
I don't know what to put here. See my description above.
Expected Results:
I don't know what to put here. See my description above.
I don't know what to put here. See my description above.
Re: severity
I'd guess major, but obviously that is just my guess. I'll so guess, and please adjust as appropriate. Thanks.
Comment 2•18 years ago
|
||
Thanks for the link Perry. Note that if you just say Bug 303595, bugzilla will link it automatically.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
I'm not sure this is a duplicate; the 2.0.0.3 upgrade seems stupider than previous ones, and more broken, because it doesn't seem to ask before trying & failing to install as a regular user, and it seems to keep retrying and failing anew.
As explained above, I don't think this is a duplicate.
2.0.0.3 upgrade seems to be a lot more broken than earlier ones.
-------------------
FireFox has been crashing every day due to the broken 2.0.0.3 upgrade
Today I logged on as admin and let it upgrade.
Now I log on as limited user, and it is still crashing, and now it insists on doing a full download -- with no cancel button!
As far as I can tell, this is a lot worse than previous updates.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
So now, even while I have this page up in firefox, I have another window saying the update was successfully downloaded and verified, and wanting to know if I want to restart firefox so it can be installed now.
I had assumed all this broken stuff would go away after I installed 2.0.0.3 as an Admin -- is the broken stuff going to persist until the next release?
Comment 6•18 years ago
|
||
I would download the Firefox 2.0.0.3 installer to your disk, then uninstall Firefox using Add Remove Programs, remove the Firefox installation directory (usually C:\Program Files\Mozilla Firefox"), then reinstall. Do all of this as an administrator.
Somewhat surprisingly, even that fails (I really thought that at least would work):
I logged out, logged in as an Admin, uninstalled Firefox 2.0.0.3, rebooted, logged in as admin, downloaded and installed FireFox 2.0.0.3, rebooted, logged in as an admin, logged out, logged in as regular (limited) user, and Firefox tells me the software update failed!
(And Firefox help/about still says 2.0.0.3)
Comment 8•18 years ago
|
||
I think it may have to do with the update information being stored in C:\Documents and Settings\user\Local Settings\Application Data\Mozilla\Firefox\Mozilla Firefox where user is your admin account name or the regular user account name. Can you check the files in the regular user account's directory and tell us what you find and who owns them?
> where user is your admin account name or the regular user account name
From the sentence after this one, I assume you mistyped here, and meant to just say "where user is your regular user account name" -- because the next sentence specifically says "regular user account's directory".
Looking to see what is there:
cd /d %USERPROFILE%\Local Settings\Application Data\Mozilla\Firefox\Mozilla Firefox
2007-03-23 20:26 <DIR> .
2007-03-23 20:26 <DIR> ..
2007-03-23 16:16 1,113 active-update.xml
2007-03-23 16:13 <DIR> updates
2007-03-23 16:16 1,113 updates.xml
2 File(s) 2,226 bytes
I checked ownership and the user owns both files and the folder, and the containing folder as well -- as you'd expect of course -- I'd be shocked if anyone else owned any of these files.
Comment 10•18 years ago
|
||
I see this report has grown to reiterate a little bit of what I have said in bug 374900. Starting with 2.0.0.2 FF lets restricted users attempt an update, why - I have no idea - see my post about the negatives. The update routine then gets confused. If you are getting the "One or more files could not be updated. ..." error, you need to remove the files you mentioned above (again see my post).
Comment 11•18 years ago
|
||
yeah, let dupe forward.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 12•18 years ago
|
||
So the fix is to uninstall firefox completely, install the new version, and then go to every single user's local settings app directory and delete all those files?
That's pretty terrible?
Comment 13•18 years ago
|
||
Only for those users that have initiated an update I would think, and yes the situation isn't that great. If they don't get the bogus update message, they can ignore it. We'll have to do something about it but you are where you are now and not where you'll be in 6 weeks.
Comment 14•18 years ago
|
||
You don't need to completely uninstall FF. Just perform updates with an account with proper priviledges. Then, yes, delete the downloaded update for each user who downloaded it.
You need to log in
before you can comment on or make changes to this bug.
Description
•