After update Firefox cannot show any web pages.

RESOLVED INVALID

Status

()

--
critical
RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: h_atac, Unassigned)

Tracking

3.5 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Safari/530.17
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)

Today, I was browsing the net, then firefox said, it downloaded 3.5.2 update, and is it ok to restart firefox. I said ok. But when firefox restarted it couldn't connect any web page at all.. I checked with other browsers, there is no connection problem at all. BTW, I don't use any proxy.

Reproducible: Always

Steps to Reproduce:
1. Update to 3.5.2
2. Restart firefox
Actual Results:  
Firefox couldn't connect to any web pages. It only shows:

Unable to connect

Firefox can't establish a connection to the server at en-us.www.mozilla.com.

    *   The site could be temporarily unavailable or too busy. Try again in a few moments.

    *   If you are unable to load any pages, check your computer's network connection.

    *   If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

Expected Results:  
Firefox should have worked normally.

I have adblocker, noscript, foxmarks installed but these add-ons were always installed so I don't think that's relevant.
(Reporter)

Updated

9 years ago
Version: unspecified → 3.5 Branch
(Reporter)

Comment 2

9 years ago
Yes, weird thing was, Symantec didn't report it as changed. It usually reports when EXE changed right away. This time when I double click Symantec's tray icon it detected the change and when I confirmed everything returned back to normal. Thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.