Red Hat Bugzilla – Bug 171955
No update button in preferences->advance
Last modified: 2008-05-01 11:38:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-TW; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
when I go edit -> preferences -> advancedd
there is no update button to update the firefox and the extensions.
right click any installed extensions in the extensions windows (tools-> extensions in the main firefox window), choose update, the update windows doesn't show up at all.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.right click any installed extensions in the extensions windows (tools-> extensions in the main firefox window)
3.the update windows doesn't show up at all. (no errors messages/dialog/crashes pop up)
Actual Results: no errors messages/dialog/crashes popped up after I reproduce the steps.
I cannot update my installed extensions, although there is updates for extensions out there.
Expected Results: the firefox should update my extensions. and have the updated extensions installed after I restart the firefox.
no errors messages/dialog/crashes popped up
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Distribution against which this bug was reported is no longer supported; could
you please reproduce this with the updated version of the currently supported
distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out
to still be reproducible, please let us know in this bug report. If after a
month's time we have not heard back from you, we will have to close this bug as
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
We haven't got any reply to the last question about reproducability of the bug
with Fedora Core 6, Fedora 7, or Fedora devel. Mass closing this bug, so if you
have new information that would help us fix this bug, please reopen it with the