OK I'll try to address everything I can in one post.
However, since NIS 5/ NAV 12 are no longer in beta, and have these serious issues, it is Symantec's responsibility to address these issues and fix them. While I do understand that some issues take time to fix, 2 months with not a single fix is unacceptable. Surely, you must agree, right?
We've released several fixes so far. You may have noticed that Norton Firewall is now version 5.0.1, Norton Licensing is version 1.0.2 and Norton Identity is 2.0.1. We're releasing fixes as soon as fast as can, and we have a major release planned for later this year. Rest assured we're working on everything we know about and more.
I've come to see how about firefox toolbar fix is coming along?Is it going to be released anytime soon? I ask because I still experience the same issues of firefox constantly freezing up when I'm browsing in a page after about 30 minutes or an hour possibly. I thought firefox 8 would fix the issue but sadly it has not.
I don't think this is a known issue. I definitely use the product on a daily basis (it's on all my home and work machines) and haven't noticed this. I just scanned the forums and didn't see this posted before. I'll ask our QA to look into this, but we may have to ask for more information.
In addition any news on the activation issues? I still experience those as well as the virus protection turning off on its own. How much longer tool we have to wait for an update? Although I understand you guys are seriously busy and there is so much you guys can do, it has been 2 months in I thought it was an update already. Are we getting any close to a fix?
We know about this issue, and are working on a fix, but as always I'm not allowed to say when it will be released. It's not actually something that's been reported by the formal support channels (technical support) so we don't think it's very widespread. However we are definitely trying to fix it "as soon as possible".
At least Firefox has gotten some support. Safari 5.1 users are still without phishing/Safe Web protection.
This is an ongoing project. Rest assured we are working on it, but please understand that Apple actually broke all ability to perform the functionality we need--there is no way to run C++ code inside Safari anymore, and we obviously don't want to try and circumvent the restrictions Apple put in place. So this is going to be a long-term project that I can't provide any further insight on at this time. Apple knows we are not the only vendor that needs this capability, and several of our competitors are also broken or have limited functionality in Safari.
P.S. Add the Vulnerability Protection error -34 and Error Reporting Daemon 65280 console log spam to the "How much longer... ?" list. Apparently the ERD problem has gotten so annoying that launchd is now throttling it:
The Vulnerability Protection error is being looked at. As I stated earlier, it's not a critical error because nothing bad is actually happening; it's an erroneous error being reported. We are probably just going to ignore this error in the future and not report it. But it will be addressed one way or the other soon. The ERD problem is not really a problem either. We actually ask launchd to throttle our error reporting daemon; it's somewhat annoying that launchd always announces that it is throttling the launch when that's what we asked it to do in the first place. We tell launchd to often every so often, but not more than X times per hour. That's what launchd is saying. I can't say if/when this one will be fixed since we don't control launchd.
I had no idea mine turned off either and I was back on "trial" until I checked Status... and what's worse it's been 2 months and no fixes for none of these issues. While I do understand they can only do so much at once, this is an unacceptable wait for a "finished" product. I feel like I paid for a beta product since these issues are still not ironed out.
This is a known issue and we're working on a fix. It's corporate policy to never pre-announce product release dates but "end of year" is a good time to check back.
The Firefox issue where is just sits "Connecting to [page.page.com]
I assume this is the same issue reported above. I've never seen it personally, but I'll ask our QA to try and reproduce it.
Also, please remember that these forums are helpful, but are not considered an official source of technical support. If you are experiencing a problem and don't see a fix for it mentioned here on the forums, the official way to notify us is to call technical support. That's the sure-fire way to make sure our team knows about the issue, because we don't always have the time to check the forums.
Ryan McGann
Principal Software Engineer
Macintosh Products & Solutions
Symantec
