Closed Bug 426138 Opened 17 years ago Closed 15 years ago

Firefox fails to launch if Netbarrier's info hiding is on

Categories

(Firefox :: Extension Compatibility, defect)

2.0 Branch
PowerPC
macOS
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: curtispsf, Unassigned)

Details

(Whiteboard: [CLOSEME 2010-10-15])

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 Firefox 2.0.0.13 would not launch. Did a clean system install and problem persisted. I tried to launch FF through it's safe mode but was unable to do so. I then booted the system (10.4.11) in safe mode and Firefox launched and operated properly. I narrowed the conflict to Intego Netbarrier's Info Hiding preferences. Even though FF initially would hang, info was coming through as the "latest headlines" bookmark was current. Reproducible: Always Steps to Reproduce: 1. Turn on Netbarrier info hiding.. Try to launch Firefox. No go. Could not troubleshoot in Firefox safe mode. 2. Do a system safe boot or turn off Netbarrier's info hiding. 3.Firefox then launches Actual Results: Install both Firefox 2.0.0.13 and Netbarrier. Turn info hiding on in Netbarrier. Try to launch Firefox. Unable to troubleshoot Firefox in its safe mode. Disabled Netbarrier's info hiding and Firefox launched with no hangs. Expected Results: Firefox should launch (like Safari and prior versions of Firefox) with Netbarrier info hiding engaged. I find it difficult to believe this apparent conflict between Firefox 2.0.0.13 and Netbarrier hasn't been reported earlier. However, this conflict persisted through 2 OS X systems (old system and new clean system installs). I will obtain another computer with OS X 10.4.11 AND NETBARRIER and try to recreate this supposed "bug". All I am able to say with certainty is that I experienced the same problem 2 times on 2 OS 10.4.11 systems on the same computer (G4 Powermac)
http://www.apple.com/downloads/macosx/networking_security/netbarrierx5.html External firewall it seems, have you contacted Netbarrier? They probably haven't added the latest firefox to their safelist yet.
I narrowed things down and found what i thought was an anomaly which then made sense, sort of. The Netbarrier Surf tab which Initially causes Ff 2.0.0.13 to hang is the "Hide information on the last site visited" tab. If this is on (blocking) then an initial launch of FF to any "new" web site will also be blocked. I am cleaning all caches and deleting what I can before closing, so each new launch to a website thinks this is a first time for that site. This bug requires that that tab be off so that I am identifying myself to that site; when I do so, all subsequent launches to that site will go thru fine, even with the hiding reingaged. But when I then go to another site, I must repeat the process....ie identifying myself to anyone I haven't met before, and so on....
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Severity: critical → major
Version: unspecified → 2.0 Branch
Reporter, are you still seeing this issue with Firefox 3.6.10 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-10-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.