Closed
Bug 388867
Opened 18 years ago
Closed 16 years ago
Firefox attempts to install the update to 2.0.0.5 in a WindowsXP restricted account
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: m.w.sachs, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.5) Gecko/20070713 Firefox/2.0.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.5) Gecko/20070713 Firefox/2.0.0.5
Firefox updated itself to 2.0.0.5 today. I logged onto Administrator for the update. The update was applied with no problem and Firefox runs normally in the administrative accounts. In my normal restricted account, "About Firefox" now shows version 2.0.0.5. However, every time I start Firefox in the restricted account, it again attempts to install the update and complains that it (obviously) does not have the necessary permissions. How can I get it to stop trying to update itself again in the restricted account?
Reproducible: Always
Steps to Reproduce:
1. Every time Firefox starts in a restricted account, it attempts to update to 2.0.0.5 although it has already been udpated.
2.
3.
Actual Results:
Start Firefox in a WindowsXP restricted account after having updated it to 2.0.0.5 in an administrative account.
Expected Results:
Firefox displays its installation failure message and then the site I was going to is displayed.
Firefox should recognize that it has already been updated.
Comment 1•18 years ago
|
||
Could you take a look at http://kb.mozillazine.org/Updates_reported_when_running_newest_version if this helps to fix your problem ?
The Problem that normal users are asked for the update that they cannot apply is covered in Bug 383518
Component: Installer → Software Update
QA Contact: installer → software.update
| Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
Comment 2•16 years ago
|
||
No reply to comment #1 in well over a year so resolving incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•