Please Sign In with Norton Account to Ask a Question or comment in the Community
Product Announcement: Norton Security 22.23.4.6 for Windows is now available!
Posted: 01-Feb-2009 | 8:52PM · 24 Replies · Permalink
What is happening here? Log does not actually get written to Library/Logs/CrashReporter. This seems to be related to the self-unlock problem which has become much less frequent recently.
http://community.norton.com/norton/board/message?board.id=norton_mac&thread.id=64
10.4.11 with all updates
Posted: 01-Feb-2009 | 8:52PM · Permalink
What is happening here? Log does not actually get written to Library/Logs/CrashReporter. This seems to be related to the self-unlock problem which has become much less frequent recently.
http://community.norton.com/norton/board/message?board.id=norton_mac&thread.id=64
10.4.11 with all updates
Posted: 03-Feb-2009 | 7:11PM · Permalink
Posted: 04-Feb-2009 | 7:17PM · Permalink
Posted: 04-Feb-2009 | 10:27PM · Permalink
Is the padlock in the NAV app always unlocked?
What about if you let the machine sit for 10 minutes without any activity or input and then launch the NAV app? Is it still unlocked?
Posted: 05-Feb-2009 | 7:57PM · Permalink
Posted: 05-Feb-2009 | 8:15PM · Permalink
x190av wrote:
I find it unlocked at startup (even though it was locked at shutdown). I then lock it and it stays that way until the next restart, AFAIK.
How soon after startup are you launching NAV? If you launch NAV 20 minutes after startup is the padlock still unlocked?
Posted: 06-Feb-2009 | 9:57AM · Permalink
Posted: 06-Feb-2009 | 9:58AM · Permalink
Just did my weekly LiveUpdate, which took over 5 mins. just to process, but was eventually successful. For now, as after last weeks update, NAV is locked after restart (last week that lasted about 2 days). However, still getting enteries in var/log/ crash reporter (see last entry on my initial post).
Duplicate post, sorry! How to delete?
Message Edited by x190av on 02-06-2009 10:09 AM
Posted: 06-Feb-2009 | 10:04AM · Permalink
x190av, you didn't answer my question.
What happens if you:
1 restart/startup
2 wait 15-20 minutes
3 launch NAV app
is padlock locked or unlocked.
For an admin account the padlock will be open for approx 5 minutes after a login/startup -this is because the system has just been authenticated during the login process.
Also in-terms of the crash at shutdown, that is a different issue and is likely related to FileVault. Are you using FileVault on that account?
Posted: 06-Feb-2009 | 10:19AM · Permalink
Timothy wrote:x190av, you didn't answer my question.
What happens if you:
1 restart/startup
2 wait 15-20 minutes
3 launch NAV app
is padlock locked or unlocked.
For an admin account the padlock will be open for approx 5 minutes after a login/startup -this is because the system has just been authenticated during the login process.
Also in-terms of the crash at shutdown, that is a different issue and is likely related to FileVault. Are you using FileVault on that account?
re: lock issue Will do further testing and post results.
re: crash issue Yes, I use FileVault.
Posted: 06-Feb-2009 | 5:52PM · Permalink
[quote]
What happens if you:
1 restart/startup
2 wait 15-20 minutes
3 launch NAV app
is padlock locked or unlocked.
For an admin account the padlock will be open for approx 5 minutes after a login/startup -this is because the system has just been authenticated during the login process.
[/quote]Seems to behave the way you described it--unlocked for ~5 mins, then locked for remainder of session. Seems to be rather insecure behaviour for a security application, although I believe Symantec has indicated they may change this in future releases.
That be as it may, my purpose in starting this thread was the SymDaemon crash, which continues unabated on each shutdown (restart). Any comments on this 'devilish' issue, Symantec?
Posted: 06-Feb-2009 | 6:10PM · Permalink
I think that the crash on logout is related to the combination of FileVault and AutoProtect.
Try turning off AutoProtect and see of the crashes stop.
I discussed this issue with Symantec Project Manager Mike Romo on 3/6/08. He informed me that NAV 11 is 'not really' compatible with FileVault, but suggested that the issue could be resolved in a future update.
I attempted to follow-up with him on 9/15/08, but he responded that he was too busy to spend time on the issue.
Posted: 07-Feb-2009 | 8:11PM · Permalink
Timothy wrote:I think that the crash on logout is related to the combination of FileVault and AutoProtect.
Try turning off AutoProtect and see of the crashes stop.
I discussed this issue with Symantec Project Manager Mike Romo on 3/6/08. He informed me that NAV 11 is 'not really' compatible with FileVault, but suggested that the issue could be resolved in a future update.
I attempted to follow-up with him on 9/15/08, but he responded that he was too busy to spend time on the issue.
"Try turning off AutoProtect and see if the crashes stop."
SymDaemon still crashes with AutoProtect off.
Posted: 09-Feb-2009 | 10:50AM · Permalink
Hi,
SymDaemon is not currently used by AutoProtect, so the crash is probably related to another feature of Norton AntiVirus. Could you please private message me your e-mail address, so I can get more information to investigate this problem?
Also, please try looking if
* Vulnerability Protection is turned off, and if so, try turning it on
* What product you have installed (Norton Internet Security, Norton AntiVirus, etc.)
Thanks, and sorry for the problems.
Ryan
Posted: 18-Feb-2009 | 11:42AM · Permalink
Posted: 31-Mar-2009 | 9:58PM · Permalink
Ryan,
Any way to stop your application from crashing?
Does anyone else get these log entries?
Thanks,
x190av
Message Edited by x190av on 03-31-2009 10:01 PM
Posted: 01-Apr-2009 | 11:38AM · Permalink
Hi Jay,
We have actually reproduced this crash in house. It's sort of machine specific, since obviously not everybody is getting these entries, but we did find another user who is getting them.
Unfortunately I can't comment on when a fix will be released. I will definitely keep you in the loop, and thanks for bringing this to our attention.
As for a temporary workaround, I'll have our QA look into it. It sounds like it is just a timing issue, so I am not sure there is much to do. I'll let you know if we find a workaround.
Thanks,
Ryan
Posted: 01-Apr-2009 | 9:38PM · Permalink
ryan_mcgann wrote:Hi Jay,
We have actually reproduced this crash in house. It's sort of machine specific, since obviously not everybody is getting these entries, but we did find another user who is getting them.
Unfortunately I can't comment on when a fix will be released. I will definitely keep you in the loop, and thanks for bringing this to our attention.
As for a temporary workaround, I'll have our QA look into it. It sounds like it is just a timing issue, so I am not sure there is much to do. I'll let you know if we find a workaround.
Thanks,
Ryan
Thanks for your reply. As a non-expert, what I would like to know is whether this issue can cause problems elsewhere in my system?
x190av(Jay)
Posted: 01-Apr-2009 | 11:06PM · Permalink
While I can't speak with 100% certainty, there is a very low risk for this to affect anything on your computer, aside from making system shutdown take a couple seconds longer.
The only down side for your computer, besides the couple seconds of delay in shutdown, is that it will create a crash report for every shutdown, so you may want to clean out the CrashReporter folder every once in a while. Sorry about that.
Ryan
Posted: 07-May-2009 | 10:33PM · Edited: 07-May-2009 | 10:33PM · Permalink
This issue seemed to have been fixed with late April's update and then you broke it again a week later. What gives? Please do more testing before releasing updates, particularly since they seem to be quite difficult for the OS to install.
Posted: 07-May-2009 | 11:07PM · Permalink
I actually don't think the NAV 11.0.2 inline was supposed to fix this issue. If you didn't see it for a period of time, that was entirely coincidental. We're still working to fix this issue.
Thanks,
Ryan
Posted: 10-May-2009 | 12:09AM · Permalink
Ryan,
Please read this!
See Nuchida's post of 20-4-2009
nuchida
Message 33 of 34
Viewed 661 times
tomhuff wrote:This isn't the only problem either. In addition to this problem, we are still awaiting a fix for the " SymDaemonCrash.Log "
On a less critical note (only because it is never seen by 98% of my clients or Symantec product users), is the whole "SymDaemon.crash.log" issue. I'm sure you are aware of this also, but it is where the following log file:
/var/log/crashreporter.log
produces this message every time the system is shut down:
Wed Apr 8 00:27:19 2009 crashdump[875]: crashdump started
Wed Apr 8 00:27:20 2009 crashdump[875]: Started writing crash report to:
/Library/Logs/CrashReporter/SymDaemon.crash.log
but yet the log:
/Library/Logs/Crashreporter/SymDaemon.crash.log
...is always empty?
Thomas,
I hope this will be fixed by the upcoming NAV 11.0.2 patch. We are publishing it right now and it should be available within the hour.
Please let me know if it prevents your SymDaemon crases.
Thanks!
This thread is closed from further comment. Please visit the forum to start a new thread.