Closed Bug 268560 Opened 20 years ago Closed 19 years ago

Critical updates available (red icon present) after update is successful.

Categories

(Toolkit :: Application Update, defect)

Product:
Toolkit
Component:
Application Update
Version:
1.7 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: craig, Assigned: bugs)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Just installed firefox 1.0. 
Restarted browser.
The red arrow is showing in the top right hand corner saying
"critical updates available"
already?


Reproducible: Always
Steps to Reproduce:
1.
2.
3.
I have the same problem. The red Critical Update(s) Available icon is showing. I
am using the MacOSX version of Firefox... I click the icon, it searches for
updates. The update box is empty and the alert icon will not go away.
I still think this is a bug but I have figured out how to make the update icon
disappear. I note that when I did click on the "updates" icon, the option was to
check Firefox and extensions for updates, but after doing so, the list of
updates to chose from was empty (maybe another bug there, that having an empty
list should automatically clear the flag). In any case, I then turned off the
auto-check feature for updates and this cleared the update arrow. Then when I
turned the auto-check arrow back on, the flag didn't reappear. I think the bug
is that if there are pending updates, but the user chooses to upgrade the
browser rather than apply the updates, then the flag isn't automatically
clearing. I would assume the correct behaviour should be to clear the flag if
the browser is updated, then check again to see whether there are any applicable
updates to apply.

Doesn't work here; I've just cleared the "check extensions and themes" option
(why only those, rather than the main browser?), and the update icon is still
there, even after restarting.

Having said that, I am using the Debian build. Could be something was changed.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0
(Debian package 1.0-2)
Re comment:
I've just cleared the "check extensions and themes" option
(why only those, rather than the main browser?), and the update icon is still
there, even after restarting.

I unchecked the lot - the extensions AND the browser, that seemed to do it.
I've seen this several times now on my home installation. In my case, it tells
me that "Firefox 1.0 is available." I even let it install it one time. That
cleared the icon for a while, but now it's back.  I'm unning on WinXP Home w/ SP2.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0


FWIW, I just installed the 1.0.1 upgrade and I still see the critical update
icon. When I click it, it finds 1.0 as the available update. Umm... no. :)
tested app update 1.0 to 1.0.1 (using test rdf and test .xpi)

Update completes successfully, yet the red critical update icon is present in
the menu toolbar near the throbber. Restart Fx; the critical update icon is
still present. Clicking the icon fires update check as expected. It finds no
updates available, then the icon disappears.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Critical updates available → Critical updates available (icon present) after update is successful.
This problem seems to be very common in WINXP-SP2.
After I updated to 1.0.1 I still had the "Critical Updates Available" Icon
active in the top-right corner.
When Firefox looks for updates, it finds none, but displays an empty list to
select which ones I want to update. When I hit the "Next" button, I get an
infinite loop in the "downloading updates" process.
Hope this helps you fix this problem.
*** Bug 284859 has been marked as a duplicate of this bug. ***
This might be profile related. After creating a clean new profile I'm not seeing
the icon. I'm hoping that it doesn't return after a day or two of browsing.
Manually forcing an update finds nothing (as expected). I've kept a copy of my
old profile so if someone in the know is interested I can provide a copy of
whatever files might affect this feature.
I removed these lines from my prefs.js file

user_pref("app.update.lastUpdateDate", 1111994888);
user_pref("app.update.updatesAvailable", true);
user_pref("app.update.url",
"http://update.mozilla.org/update/firefox/en-US-1.0-rc.rdf");
user_pref("app.version", "0.10");

and then the "critical updates available" icon went away. I am now using v1.0.2
Flags: blocking-aviary1.1+
Whiteboard: [asaP1]
*** Bug 284483 has been marked as a duplicate of this bug. ***
*** Bug 272604 has been marked as a duplicate of this bug. ***
*** Bug 288189 has been marked as a duplicate of this bug. ***
Summary: Critical updates available (icon present) after update is successful. → Critical updates available (red icon present) after update is successful.
Assignee: firefox → bugs
Component: General → Software Update
QA Contact: general → bugs
Oy, where RTFM means Ring the Family Maven and they *all* use Firefox....."(on
WinXPSP2,W2KSP4,I believe a W982nd machine. Note: when clicked on, the button
repeatedly started the process of *again* d/l'ing 1.02 - and again, and again....
 - also noted: both the icons and the "take me to Mozilla home" icon next to it
differ on fairly identical installations. I've got a white arrow in a red bullet
next to an old M-in-the-box on one machine, a red flower and a geko on another,
a red target and I forget what else on a third - something is either not
synching these or just leaving what was there when the first version of FireFox
to be loaded on the machine was loaded. Minor, not a "bug" but strange...
I DONT KNOW what happened but before my theme (little Firefox) was updated the
red splot went yellow. When I called up to see what's what, theme was updated
and splot cleared to NORMAL BLUE - this followed a long Bugzilla session
concerning something else entirely 7-Apr-05 04:15 edt


(In reply to comment #15)
> Oy, where RTFM means Ring the Family Maven and they *all* use Firefox....."(on
> WinXPSP2,W2KSP4,I believe a W982nd machine. Note: when clicked on, the button
> repeatedly started the process of *again* d/l'ing 1.02 - and again, and again....
>  - also noted: both the icons and the "take me to Mozilla home" icon next to it
> differ on fairly identical installations. I've got a white arrow in a red bullet
> next to an old M-in-the-box on one machine, a red flower and a geko on another,
> a red target and I forget what else on a third - something is either not
> synching these or just leaving what was there when the first version of FireFox
> to be loaded on the machine was loaded. Minor, not a "bug" but strange...


*** Bug 292354 has been marked as a duplicate of this bug. ***
(In reply to comment #7)
> tested app update 1.0 to 1.0.1 (using test rdf and test .xpi)
> 
> Update completes successfully, yet the red critical update icon is present in
> the menu toolbar near the throbber. Restart Fx; the critical update icon is
> still present. Clicking the icon fires update check as expected. It finds no
> updates available, then the icon disappears.
> 

Observed this exact same behaviour in every single Firefox upgrade I've done on
my win2k box, and I've been upgrading incrementally since 0.9.

This isn't a big deal, but would certainly be disconcerting for users.  You
don't expect a program to prompt you to do something you've just done.


On my laptop (winxp) with 1.04 (still), After the update, the red icon is still
on. If I check for updates, it says "updates are available" but does not show
any soecific ones!. If I check install, it just sits there installing upodates
and never finishes. So I cannot remove the red icon. I do not see this on my
desktop which also runs XP. And all the plugins on my laptop are also on my
desktop except for flashblock and targetalert.
Flags: blocking-aviary1.1+ → blocking-aviary1.1-
Whiteboard: [asaP1]
Updating to Firefox 1.0.6 behaves as comment #7.
This bug now only applies to the Firefox 1.0 branch.
Version: unspecified → 1.0 Branch
*** Bug 305285 has been marked as a duplicate of this bug. ***
Upgrading from Firefox 1.0.6 to 1.0.7 (by downloading and installing, not by
clicking on the update icon) behaves as comment #8, not as comment #7.
If this is 1.0 branch only, shoudn't it be wfm?
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Has this bug actually been fixed now or just moved somewhere else?
(In reply to comment #25)
> Has this bug actually been fixed now or just moved somewhere else?

This works as expected in 1.5 beta 1. Mainly security fixes goes to the 1.0.x
branch. (please correct me if wrong)
>> Has this bug actually been fixed now or just moved somewhere else?
>
> This works as expected in 1.5 beta 1. Mainly security fixes goes to
> the 1.0.x branch.

To translate: This has not been fixed and will not be fixed. (But that's okay.)
Because Fx 1.5 has switched to a different update mechanism this bug applies to
the 1.0 branch only. It won't be fixed there because that branch only gets
critical fixes (like security).
*** Bug 316210 has been marked as a duplicate of this bug. ***
*** Bug 316210 has been marked as a duplicate of this bug. ***
*** Bug 316958 has been marked as a duplicate of this bug. ***
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.