Closed
Bug 294782
Opened 20 years ago
Closed 20 years ago
Updating to Firefox version 1.0.4 creates total failure of the Firefox program.
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: lonngooch, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 After installing Firefox 1.0.4 from the 'critical update button' on the Firefox toolbar and after working with several Mozilla Firefox versions uneventful for over one year, downloading Firefox 1.0.4 yesterday (18 May 2005) prevents me from using the program any longer. When initiating Firefox from the installation program, start menu, or any other method which would start my default web browser (Firefox), I only receive the Alert message: "The operation timed out when trying to contact ...". Reproducible: Always Steps to Reproduce: 1.Initiate Firefox Web Browser in any usual manner (Installation program, Start Menu, etc.). 2. 3. Actual Results: Alert message: "The operation timed out when trying to contact ...". Expected Results: Open to home website or any other page requested - including mozilla.org website. I have uninstalled and reinstalled Mozilla Firefox from the Add/Remove Programs section of the Control Panel several times. I have shutdown and restarted my computer with and without Firefox installed and either restarted or reinstalled Firefox. Microsoft IE 6.0 has been operable through all of my attempts to update Firefox.
Comment 1•20 years ago
|
||
Have you tried adjusting your firewall to allow Firefox access to the internet?
Comment 2•20 years ago
|
||
Reporter it's your firewall that is blocking the new firefox-version. Note : bugziila is NOT a support database. Use the Mozillazine Forum for that.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•