Closed
Bug 421704
Opened 18 years ago
Closed 16 years ago
Firefox always shows a error because it's unable to update because of permissions problem
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: pachoramos1, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en; rv:1.8.1.12) Gecko/20080209 Epiphany/2.20 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en; rv:1.8.1.12) Gecko/20080209 Epiphany/2.20 Firefox/2.0.0.12
Hi!
I usually use firefox in my university on some computers with windows XP. Seems that Firefox was installed as Administrator, but we use them as normal users without admin privileges.
The problem is that, each time I open firefox, it tries to check updates and fails showing an error. I start firefox simply clicking on "accept" in this warning dialog, but it is a bit anoying.
I think that firefox should simply not try to update if it doesn't have enough permissions, or, at least, not show this error that makes some users think that something is "wrong".
I think that this should be fixed because firefox is being installed on some public places where users don't have privileges for installing newer firefox versions. I know that it is usually important update firefox because of security problems, but showing this errors doesn't help much because users aren't allowed to update it and administrators don't do OK their work sometimes :-(
Thanks a lot
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
I don't think you will find the answer to this problem at mozilla.org, because the problem is not the error screen at all, but is a result of how firefox was installed on the university's computers.
Probably you should send an e-mail to the university's computer department. They should be able to configure firefox on all their computers to not check for updates automatically.
| Assignee | ||
Updated•18 years ago
|
Product: Firefox → Toolkit
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•