Thanks for the advice. It was indeed a profile issue. After switching to complain mode, I got messages like
[16653.510538] type=1503 audit(1225647340.558:116): operation="inode_permission" requested_mask="::r" denied_mask="::r" fsuid=114 name="/etc/resolvconf/run/resolv.conf" pid=23644 profile="/usr/bin/freshclam" I figured that freshclam couldn't do DNS resolution because it was denied access to /etc/resolvconf/run/resolv.conf. Access to this file is only needed on systems that have the resolvconf package installed (a dependency of network-manager-vpnc). Adding the line /etc/resolvconf/run/resolv.conf r, to /etc/apparmor.d/usr.bin.freshclam and switching back to enforce mode solved the problem for me. I guess we should update the apparmor profile to include this possible configuration. -- clamav-freshclam update dns problem https://bugs.launchpad.net/bugs/292580 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
