Closed
Bug 249160
Opened 20 years ago
Closed 20 years ago
Critical Update(s) Available logo does not go away after update
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 249015
People
(Reporter: hchennings, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.8 Critical Update(s) Available logo showed up for the 0.9.1 firefox version. i installed the update. firefox started with the new 0.9.1 edition. Critical Update(s) Available logo is still present after installing the update. the logo should be gone. Reproducible: Always Steps to Reproduce: 1.Critical Update(s) Available logo showed up for the 0.9.1 firefox version. 2.double click on the logo. 3.firefox 0.9.1 is available comes up in new box. 4.download firefox 0.9.1 5.install firefox 0.9.1 6.open firefox 0.9.1 7.firefox opens with Critical Update(s) Available logo Actual Results: firefox opens with Critical Update(s) Available logo Expected Results: firefox opens with NO Critical Update(s) Available logo
Comment 1•20 years ago
|
||
Same problem with User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Comment 2•20 years ago
|
||
Not an expert here, but was this the installer or zip build? I've seen other people with this problem, both - I think - using Windows.
Same problem with Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Comment 4•20 years ago
|
||
I have the same problem. I uninstalled 0.9 and installed 0.9.1 with the windows installer. I didn't delete the profile.
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Comment 5•20 years ago
|
||
*** This bug has been marked as a duplicate of 249015 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•