Steelskin
Members-
Posts
18 -
Joined
-
Last visited
About Steelskin
-
Rank
Newbie
Profile Information
-
Location
U.K.
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Nightowl reacted to a post in a topic: Chrome 79 always starts a core dump and crashes
-
Any news on a fix for us Linux users who use Chrome, Chromium etc 😕 I see there is no mention on the Eset website. Is it too much to ask of Eset that they actually 'officially' acknowledge that there is a problem and they have a plan of action. I really do detest companies that don't keep their customers in the loop about progress (if any).
-
Nightowl reacted to a post in a topic: Chrome 79 always starts a core dump and crashes
-
Totally agree, I will be requesting a pro-rata refund based on how long it's taking Eset to resolve this. Currently my feeling is that Eset will not be receiving a renewal. This isn't open source software. We pay you good money for a product and you're not delivering a product that does what it's supposed to do. In fact open source is vastly better because at least users generally get feedback from the developers. Is there any 'official' comment from Eset about this problem and I'm not talking about any moderators comments in this forum.
-
Sometime in early December 2019. if I remember correctly, I made contact by using the interface in NOD32 for reporting problems. I've no idea where that's reported to, does it even work ? I assumed it was to HQ in Slovakia. I've searched my emails back to 1st December 2019 and have nothing from Eset about a ticket number, just a lot of emails from people reporting the problem on this forum.
-
Despite contacting Eset officially they have so far not responded. I'm not impressed to say the least. On the plus side, I've noticed my laptop feels faster in terms of how fast programs start having deinstalled NOD32. I don't know whether anybody else has experienced this. It's a fairly subtle improvement in speed but a improvement non the less. But then I guess that's to be expected when Eset is not scanning every file that's opened.
-
If you run Chrome from the command line while the Eset daemon is running, Chrome produces the following sandbox error. [5012:1:0109/230249.177870:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [5012:1:0109/230249.178539:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. If you kill the Eset daemon 'sudo pkill esets' then you don't get the above error.
-
Or will we all be requesting refunds and the associated bad press that will produce ? Really ? A bug fix in Q1/2020 and no bug fix planned for the ESET Linux Desktop Home edition ? Seriously ? 😠