Closed
Bug 346188
Opened 19 years ago
Closed 18 years ago
1.5.0.5 update hangs if Norton Internet Security Suite '06 is running
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: bugzilla, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
My experience whilst allowing the automatic update to 1.5.0.5 to install itself.
1) received pop-up window that Firefox has downloaded an update & will install the update at next program launch
2) I exit Firefox & relaunch it.
3)Firefox menu/toolbars appear, but main window is blank, hourglass turning constantly, & the circular 'churning' symbol at right of menu bar continues to turn.
4)Attempt to exit Firefox, and Firefox appears to close.
5) Attempt warm reboot, system non responsive
6)Forced hard reboot
7)After hard reboot, I disable Norton Internet Security using temporary suspend for 30 minutes
7a) NIS build is 9.1.0.33, NAV build is 12.2.0.13
8)Launch Firefox, Firefox start page appears.
9)NIS window appears warning that Firefox has changed since its last launch, and requests permission to create a new rule. I click OK, & Firefox works fine.
Reproducible: Didn't try
Please advise Symantec of your revision to Firefox. They can include this change in their next liveupdate of 'safe programs'
Although the problem is rooted in NIS, I suspect many users will attribute the problem to Firefox, because the hang is at the launch of the newly downloaded version of Firefox. You may want to remind users to disable NIS before relaunching Firefox. I've had this problem with NIS-originated conflicts in the past on other programs. I've learned to work around it - I disable NIS if an app installation procedure hangs (some installs hang, others NIS allows). However, a number of users might not know to do this & end up very frustrated with Firefox.
Thanks! I really enjoy Firefox.
Buildconfig returned:
about:buildconfig
Build platform
target
i586-pc-msvc
Build tools
Compiler Version Compiler flags
$(CYGWIN_WRAPPER) cl 12.00.8804 -TC -nologo -W3 -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 12.00.8804 -TP -nologo -W3 -Gy -Fd$(PDBFILE)
Configure arguments
--enable-application=browser --enable-update-channel=release --enable-optimize --disable-debug --disable-tests --enable-static --disable-shared --enable-official-branding --enable-svg --enable-canvas --enable-update-packaging
![]() |
||
Comment 1•19 years ago
|
||
-> Software Update
Component: Installer → Software Update
QA Contact: installer → software.update
Comment 2•19 years ago
|
||
We notified Symantec of our release, and haven't heard too many cases of this. Is it possible your definition files aren't getting updated from Symantec? Basically they keep a "whitelist" of acceptable applications, and the signatures need to be updated regularly just as the virus signatures do.
Comment 3•18 years ago
|
||
Is this a problem anymore with Firefox 2?
Comment 4•18 years ago
|
||
-> incomplete
Closed as incomplete since missing infos (see comment 2/3).
Ted, i close this report as incomplete. If you still have the same problem during updates from Firefox 2.0.0.x to 2.0.0.4, feel free to reopen.
Then it would be great if you could answer the questions from Dan`s comment
(see comment #2).
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
Version: unspecified → 1.5.0.x Branch
Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•