Closed
Bug 575115
Opened 16 years ago
Closed 16 years ago
Untitled blank white pages day after latest update 3.6.6
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: shinji.ex.0, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4) Gecko/20100611 Ant.com Toolbar 2.0.1 Firefox/3.6.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4) Gecko/20100611 Ant.com Toolbar 2.0.1 Firefox/3.6.4
Summary says it all tried refreshing page selecting a bookmark page and or entering an address plus closing and relaunching the browser to no avail
Right now I have to go to program files and select the Firfox app then restore it to previous version in order to get it working but it's only temporary
To note my Internet Explorer 8 is working correctly
I had no issues prior to operating Mozilla Firefox on my Windows 7 64bit up until your latest update
I tried to disable recent add-ons but that did not help either
Reproducible: Always
Comment 1•16 years ago
|
||
This does not appear to be a security issue and we're more likely to make progress if more people can access the bug: unhiding.
What was your prior version? I'm assuming it was 3.6.3, but if it was even earlier (such as 3.5 or even 3.0) that would be incredibly significant to know and would broaden the areas we'd want to look at.
I wouldn't just disable "recent" add-ons, go whole hog and run in "safe-mode" as a test. If that fixes it then the problem is definitely one of your add-ons being incompatible with the update, which might not be one of your "recent" ones. You can then add back add-ons to see at which point the problem recurs, and knowing which add-on is breaks will help immensely in tracking down which Firefox change is causing the problem.
You can get more help tracking this down at http://support.mozilla.com/
Apropos of nothing, your "ant toolbar" has made syntactically invalid changes to the user agent string.
Group: core-security
Comment 2•16 years ago
|
||
In e-mail the reporter says the cause was Norton disabling some Firefox libraries and the problem has now been resolved by a Norton update.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•