Closed Bug 762793 Opened 13 years ago Closed 13 years ago

lies about up to date

Categories

(Toolkit :: Application Update, defect)

Product:
Toolkit
Component:
Application Update
Version:
12 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 679742

People

(Reporter: veix26, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0 Build ID: 20120601175215 Steps to reproduce: Menu - Help - About Firefox Actual results: It says "Firefox is up to date" Expected results: Firefox should have notified me that I am not using the latest firefox. Currently I have version 12 installed, but 13 is also out. Firefox does not notify me that I am using insecure browser when there is a fix. Most likely the problem is caused by company firewall and firefox cannot actually download updates. But Firefox should be smart enough to notify that it failed to check newer updates or at least tell me that an update is available but download failed. Instead it just lies...
Severity: normal → critical
OS: Linux → Windows 7
Version: 13 Branch → 12 Branch
Actually your User Agent says you are running Firefox 13, did you file this bug with a different cumputer than your work one? I know there i a bug on if Firefox can't reach the update servers.
Yes I did and also changed it from version drop-down menu in this bug insert page. The problem appeared on Windows 7-64bit with firefox 12. Do you know in which version this bug is planned to be fixed?
I guess you are using a 32bit Firefox build on your Windows64 system, right ? (win64 builds are not official) Is that an en-us build ? The "up-to-date" message without connection is bug 679742
Component: Untriaged → Application Update
Product: Firefox → Toolkit
QA Contact: untriaged → application.update
Sounds like a dupe of bug 679742.
Yes it really is very similar to 679742.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.