Closed Bug 401818 Opened 18 years ago Closed 18 years ago

firefox stopped working after latest security update dated Oct 30th2007

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: leaf999, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; YPC 3.2.0; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 1.0.3705) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9 I am surprise that how can firefox even releases a security update which breaks the browser itself. This tells me the state of the company. I am using IE to file this issue. As soon as I updated my firefox with the Oct 30 th security update, my firefox doesnt connect to any site. On the other hand IE is working fine. Also in the Error console it show "Overflowing"......... Reproducible: Always Steps to Reproduce: 1.Start the browser and it is not working 2. 3. Actual Results: Start the browser and it is not working Expected Results: Browser should be working Problems which I used to face with IE, is now creeping up in firefox and folks responsible for releasing such a security update should be held accountable. Extremely disappointed.....
One or more of the steps at http://support.mozilla.com/kb/Basic+Troubleshooting should give you a working browser. Firefox 2.0.0.9 has not been released. What update channel are you on? http://www.oxymoronical.com/web/firefox/updatechannel will allow you to check which one you are on.
I cannot find the update channel But when I go to the help about in firefox, it shows me this: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9 Also when I try to connect it says AUS: In Update history, the last update shows Firefox 2.0.0.9 rc1
When I go and check for update I get the following: AUS: Connection Refused
So far tried safe-mode and rebooting the computer. Both didnt help.
This symptom is typical of a Firewall issue, and since we haven't officially released FF2.0.0.9 (it is on the beta channel, so ~70K users have it) some Firewall vendors may not yet have updated their whitelists. You can try check for updates from your firewall (whitelisting firewalls of this sort are usually bundled in security suites. Norton and McAfee are popular ones of this type, for instance). May not help for a day or two You can manually adjust the settings in your firewall to allow Firefox. If you can't figure out how ask for help from our technical support: http://www.mozilla.com/support/ I don't recommend it, but you could turn off your firewall temporarily, or temporarily switch to the less-strict built-in one that comes with Windows. You could switch to the "release" channel so you don't have the problem of getting ahead of your firewall definitions in the future. The easiest way is probably to uninstall FF2.0.0.9 and then re-install FF 2.0.0.8. Don't install 2.0.0.8 on top of an existing 2.0.0.9, you'll still be left on the "beta" channel. If it were me I would adjust the program settings on my firewall to allow the new version of Firefox, I only include the other options for completeness (and because sometimes the firewall options can be hard to find).
Thanks for the help. I checked firewall and my windows firewall is OFF, but my NORTON firewall was still ON. I turned it OFF and viola things started working. Very much appreciated your help. Hopefully I can get it to work for now, till I have an update for Norton firewall.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
If you can find it, there is a setting in Norton that will let add Firefox 2.0.0.9 to the approved list without having to turn the whole firewall off (I wish I could be more specific but I don't have that product).
Yes I was able to find the option to add firefox as an exception rule in Norton Firewall to permit all. Now it is working. Thanks again for everyones help, as this was driving me nuts.....
Resolution: WORKSFORME → INVALID
You need to log in before you can comment on or make changes to this bug.