yossarianuk

It used to work fine in ububntu 16.04 and older version of eset. Seeing as all version of Ubuntu has apparmor do you not support Ubuntu then ? If I comment the line out i can still use nod32 but it disables realtime scanning, in that case I would be better off using Clamav which has zero cost...

Hi. Just installed ubuntu 18.04 - installed latest eset (Version: 4.0.90.0). Once installed and rebooted I am unable to run any local KVM vm's. It is due to the entry added to /etc/ld.so.preload libesets_pac.so When I start any KVM VM on the local machine I get the warning Error starting domain: internal error: cannot load AppArmor profile 'libvirt-1811665e-455d-4673-a10d-c5ae9b5028e7' And journalctl shows this, as you can see it is due to the library that eset adds -> libesets_pac.so Oct 03 12:50:25 mcox-N552VW libvirtd[4197]: 2018-10-03 1

I am running KDE neon (based on ubuntu 16.04 (although same happens with Ubuntu 16.04, 16.10, 17.04), I have a Nvidia GPU (hybrid GPU) Once I have installed nod32, I cannot install any nvidia updates to my system ( I believe the same thing happens with a kernel update) To make matters worse when attempting to install/reinstall the nvidia package it leave apt in a broken state with uninstalled nvidia driver, if I were to reboot in that state I would have a bricked desktop. (i.e no X..) If I either try to upgrade the kernel package or change the nvidia driver apt gets stuck - I be

I am running Kubuntu 16.04 (although same happens with Ubuntu 16.04), I have a Nvidia GPU. Once I have installed nod32, I cannot install any kernel or nvidia updates to my system. To make matters worse when changing the nvidia package it leave apt in a broken state with uninstalled nvidia driver, if I were to reboot in that state I would have an unbootable system (at least to the desktop) If I either try to upgrade the kernel package or change the nvidia driver apt gets stuck - I believe this is due to re-creating the initrd file... i.e (during a kernel update) .... run-parts: executing /