Closed Bug 527975 Opened 15 years ago Closed 15 years ago

Initial opening of Mozilla Firefox

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: HCMcGinn, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) I an running this version of Firefox: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) I am repeatedly experiencing the same following situation. When I open firefox initially after starting my laptop or after being offline for ten or more minutes, I get a Google search results, not my designated HOME page, which happens to be AT&T. This started after I downloaded the above-stated version of Firefox several days ago. I DO NOT want this, as I have to shut down & restart the browser every time. DAMNED aggravating. I have been unable to locate any setting to correct this problem. WHAT IS GOING ON?????????????????????? I need to correct this NOW. THanks, Reproducible: Always Actual Results: Google Search results (EVERY TIME) Expected Results: AT&T Home page, with my preferences, as I USED TO be able to go to every time I started Firefox.
Severity: normal → major
Priority: -- → P1
Version: unspecified → 3.0 Branch
Your build is rather old; please download the latest Firefox 3.5 version: http://www.mozilla.com/en-US/ And start it up with a new profile: http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile
Priority should only be set by developers please. resetting to -- See https://bugzilla.mozilla.org/page.cgi?id=fields.html#priority no response to comment 1, so closing incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Priority: P1 → --
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.