Norton Crashguard interfering with Talkback?



Core Graveyard
Talkback Client
16 years ago
9 years ago


(Reporter: WeirdAl, Assigned: Shiva Thirumazhusai)


Windows 98

Firefox Tracking Flags

(Not tracked)




16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20010913

I've been downloading Talkback builds from for a very, very long
time now.  Yet today was the first crash I had where I actually saw a Talkback

I have three machines which I am responsible for.  One is a Win95c machine
(currently down for an unrelated hardware problem), one is a Win98 machine my
boss owns, and one is a Win98SE machine.  The first two have Norton Systemworks
3.0 (including Norton Crashguard) on them.    This machine does not have
Systemworks or Crashguard on it yet.  (I have this thing about not pirating

I have seen crashes in the past on the other two machines in both Netscape 6 and
Mozilla -- but never a Talkback program notice.  I was actually surprised to
discover what Talkback looked like, by seeing a crash on the third machine.

I haven't used Mozilla very much on this third machine.

Reproducible: Always
Steps to Reproduce:
1.  Crash the browser on a machine using Norton Crashguard.

Actual Results:  Norton Crashguard intercepts the crash.  No Talkback program
starts up.

Expected Results:  Talkback starts up and Norton Crashguard intercepts the crash.

I don't know how many times I could have sent Talkback data in.  I would have,
had the dialog popped up.  Maybe someone needs to put FullCircle in touch with
Symantec, because I really love the Talkback feature.  It just never worked for
me before (I thought the Talkback had been automated for Gecko browsers).
Ever confirmed: true

Comment 1

15 years ago
I use Bugtoaster from and no interference occurs.  Both programs,
Bugtoaster and Talkback catch the crash.  I send the data for both programs. 
The programs of Bugtoaster once worked on Norton CrashGuard.  The difference is
that Bugtoaster collects crash data and CrashGuard recovers from crashes.  Maybe
that is what causes this.


15 years ago
Blocks: 163294

Comment 2

15 years ago
Making myself the QA contact.  I am currently investigating this problem.  I
will post any info I find from my testing.
QA Contact: chofmann → jpatel

Comment 3

15 years ago
Brant has a point and the more I think about it, the behavior the reporter sees
seems to be correct.   Since Norton CrashGuard is for crash recovery (not crash
informatin collection/reporting) makes a little sense that Talkback does
not popup after a crash.

I'm not sure what we can really do to intercept the crash before CrashGuard gets
to it, but clearly the Norton software is getting to it first and not allowing
the crash to get to the point of triggering Talkback.

Alex:  I am not familiar with Norton CrashGuard...but are there any settings
that you might be able to tweak with to see if Talkback comes up?  Are you even
still seeing this problem? (it's been about a year since you logged this bug).

Comment 4

15 years ago
:( The two machines I noticed this bug on are not easily accessible to the Net 
right now.  Likewise I haven't worked with Norton software installed for a 

The behavior is correct?  Does that mean this bug is INVALID?  :(

Comment 5

15 years ago
I wouldn't call it invalid...but we need to figure out a way for Talkback to
still work with the CrashGuard running.  It would be nice to have Talkback fire
up first (and get whatever information it needs) and then let CrashGuard do
whatever it wants to do with the crash.

We need to leave this one open for more investigation...

Comment 6

15 years ago
Norton CrashGuard was _Officially_ EOL'ed a while back. It's totally unsupported
by Symantec, and really a useless program in the post-Windows95a era. It was
officially discontinued as of September 2000.

As a Windows-centric tech/consultant, I always recommend uninstalling CG to
clients, and would recommend the same thing to folks who thi sbug would affect...

Comment 7

15 years ago
Based on the last comments, i'm going to mark this won't fix.  if anyone finds a
reason to investigate this bug further, please feel free to reopen, but if the
product no longer "exists" and is not supported, people should just uninstall it
if they are crashing.
Last Resolved: 15 years ago
Resolution: --- → WONTFIX

Comment 8

15 years ago
Agreed, which was the point of my posting that URL. Verifying.


9 years ago
Component: Talkback Client → Talkback Client
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.