Closed Bug 178564 Opened 23 years ago Closed 23 years ago

Quitting TalkBack causes a kernel panic on Mac OS X 10.2.1 (Norton AutoProtect conflict?)

Categories

(Camino Graveyard :: General, defect, P1)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: lrivers, Assigned: saari)

References

Details

(Keywords: crash)

If talkback launches, I get a kernel panic on quit.
Same thing happened to me yesterday. Had to restart my Mac... First time in six months. Grrrr...
Does it happen if you just run TalkBack manually, then quit it? By "kernel panic", do you mean the whole OS crashes? (Looks like we could use a TalkBack component for Chimera.)
Severity: blocker → critical
Keywords: crash
By quitting I mean Talkback:Quit menu item. Talkback does not connect on my machine. By kernel panic I mean OS dies, screen dims, must pull plug and reboot. This crash is as bad as it gets...
WorksForMe using TalkBack 2.0b1 (included with Chimera/2002110415) on 10.1.5. I run it, and quit just fine.
Summary: Quitting talkback causes a kernel panic → Quitting TalkBack causes a kernel panic
May require 10.2.x Whenever I see Talkback launch, I force quit it. I can't afford Kernel Panics...
I can confirm this with OSX 10.2.1. Everytime I try to quit Talkback (after a Chimera crash), I get a multilingual message telling me I have to restart my Mac. Last time, it happened after the restart : when I launched Chimera, Talkback appeared and when I chose to put it off, my Mac crashed again.
Marking confirmed per comment 2 and comment 6.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Quitting TalkBack causes a kernel panic → Quitting TalkBack causes a kernel panic on Mac OS X 10.2.x
I've never seen Talkback crash on a 10.2 machine; there must be more to this. For this who can reproduce it, what other custom software do you have installed (espeically things that install kernel extensions)? Also, please attach the /Library/Logs/panic.log file that should be present when you reboot after a kernell panic.
Priority: -- → P1
The MacFixIt report mentions an 'IdeaSpiral' file corrupted after re-booting but the only IdeaSpiral I can find info on is some kind of word processor.
Priority: P1 → --
I have been using talkback (twice) under 10.2.x and 0.6 or more current nightly builds without any problem.
I have the same problem : Computer : Ibook2 (white) 600Mhz G3 MacOsX Version : 10.2.1 Build 6D52 Chimera version : 0.6 Build 2002110604 TalkBack version : 2.0b1 I confirm than the crash occur when 1) Lauch TalkBack 2) Use the Option+Q ContrOl key or clicling on "Quit" whith mousse I have the problem both after a Chimera crash and after launching manualy TalkBack (inside Chimera.app). The problem : As said by Christian & Lorin the system Crash completly whith a splash streen in English, French, German and i supose Japan. The Splash screen said than You have to shutdown the computer whith the On/Off Button. The Splash Sreen is finished by a string : FF:FF:FF:FF:FF:FF Sorry, Simon there is no /Library/Logs/panic.log file at all after crash But your right about the "custom software" ;-) I have tested to allow/disallow some startupitems from /Library/StartupItems with the "Diablotin" Tool PrefPane Crash seem to occur when "NortonAutoProtect" is activated ! Norton Utilities version : 7.0.2r014 So the workaround is to desactivate the Norton AutoProtect tool.
Priority: -- → P1
Summary: Quitting TalkBack causes a kernel panic on Mac OS X 10.2.x → Quitting TalkBack causes a kernel panic on Mac OS X 10.2.x (Norton AutoProtect conflict?)
Thank you for that valuable information. Are there any others here who can verify that this problem is a conflict with Norton Antivirus software?
There is one thing I can confirm : Norton AutoProtect was activated when the crashes occured.
I, too, have Norton AntiVirus installed, and every time TalkBack is triggered by a Chimera crash, I get the grayed screen with the "You must restart" message upon quit of TalkBack. I have only experienced the problem on Chimera > 0.5 and while running OS X 10.2.1 (I am now running 10.2.2, but have not had the "pleasure" of a crash since upgrading last night). I also receive the FF:FF:FF:FF:FF:FF address.
I'm not able to reproduce this issue on a machine running 10.2.2, with an up-to-date Norton Antivirus installation (NortonAutoprotect binary from Sept 9 2002). Need more details on system version etc.
For those who can reproduce this crash: what version of Norton Utilities are you running? I can't repro the crash with 8.0.4 (the most recent).
Good news. Since I upgraded to MacOS X 10.2.2, my Mac doesn't crash anymore when I quit Talkback. Thought you should know.
Version of Norton Antivirus is : 8.0.4 But me too i can't reproduce anymore the crash since i have upgraded to Os X 10.2.2. Seems then this bug is specific to Os X 10.2.1 (perhaps an Apple bug and not a Talback one.)
There are no other reports of talkback panics in Bugzilla. Seems specific to 10.2.1
Blocks: 12985
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Summary: Quitting TalkBack causes a kernel panic on Mac OS X 10.2.x (Norton AutoProtect conflict?) → Quitting TalkBack causes a kernel panic on Mac OS X 10.2.1 (Norton AutoProtect conflict?)
You need to log in before you can comment on or make changes to this bug.