Jump to content

yossarianuk

Members
  • Posts

    4
  • Joined

  • Last visited

  • Days Won

    1

yossarianuk last won the day on September 20 2016

yossarianuk had the most liked content!

About yossarianuk

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.

Recent Profile Visitors

848 profile views
  1. 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...
  2. 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 11:50:25.922+0000: 4202: error : virCommandWait:2601 : internal error: Child process (LIBVIRT_LOG_OUTPUTS=3:stderr /usr/lib/libvirt/virt-aa-helper -p 0 -c -u libvirt-1811665e-455d-4673-a10d-c5ae9b5028e7) unexpected exit status 127: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (failed to map segment from shared object): ignored. Oct 03 12:50:25 mcox-N552VW libvirtd[4197]: Inconsistency detected by ld.so: rtld.c: 720: init_tls: Assertion `i == GL(dl_tls_max_dtv_idx)' failed! Oct 03 12:50:25 mcox-N552VW libvirtd[4197]: 2018-10-03 11:50:25.922+0000: 4202: error : AppArmorGenSecurityLabel:472 : internal error: cannot load AppArmor profile 'libvirt-1811665e-455d-4673-a10d-c5ae9b5028e7' If I comment out the line in /etc/ld.so.preload it works perfectly. How can this be fixed, at the moment I have had to comment out that line.
  3. 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 believe this is due to re-creating the initrd file.. Which the on-access scanner prevents.... i.e (during a kernel update) .... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-28-generic /boot/vmlinuz-4.4.0-28-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-28-generic /boot/vmlinuz-4.4.0-28-generic -> It gets stuck here - the only way to get out is to CTRL+Z (background it) - then kill the apt pid - this leave apt broken and you have to do a 'sudo dpkg --configure -a' but that cannot complete whilst eset nod32 is installed - it also gets struck As soon as I uninstall nod32 apt works as expected... It seems related to the regeneration of the initrd file, please can you investigate this as it makes the product unusable on ubuntu systems (and WILL leave non advanced users with broken systems) It is not just me having the issues I have seen a few threads i.e https://ubuntuforums.org/showthread.php?t=2329082&page=7 hxxp://askubuntu.com/questions/768892/kernel-update-gets-stuck-ubuntu-16-04-kernel-4-4-0-22/818637#818637 I posted a thread months ago but got no response .... The only 'solution' I have found is to comment out # libesets_pac.so in /etc/ld.so.preload -> If I do that kernel/nvidia updates work as expected - but the on-access scanner is broken (I can test with the EICAR test virus) Other than having to uninstall then reinstall eset nod32 at EVERY kernel or nvidia update what solution can be offered? If I have no on-access scanner I may as well be using Clamav. edit : This appears to be fixed in the latest version 4.0.85 Is there a mechanism to upgrade the version of nod32 ? Or is it just a manual install each time.
  4. 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 /etc/kernel/postinst.d/apt-auto-removal 4.4.0-28-generic /boot/vmlinuz-4.4.0-28-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-28-generic /boot/vmlinuz-4.4.0-28-generic -> It gets stuck here - the only way to get out is to CTRL+Z (background it) - then kill the apt pid - this leave apt broken and you have to do a 'sudo dpkg --configure -a' but that cannot complete whilst eset nod32 is installed... Once I have uninstalled nod32 apt works fine. It seems related to the regeneration of the initrd file, please can you investigate this as it makes the product unusable on ubuntu systems (and WILL leave non advanced users with broken systems) It is not just me having the issues I have seen a few threads i.e https://ubuntuforums.org/showthread.php?t=2329082&page=7 hxxp://askubuntu.com/questions/768892/kernel-update-gets-stuck-ubuntu-16-04-kernel-4-4-0-22/818637#818637
×
×
  • Create New...