Comment 2 for bug 1590688

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Indeed on a quick inspection it looks like both services are not running on install. It looks like for clamav-daemon this is intentional as freshclam has not run yet. However I'd expect the freshclam service to start. After starting it manually, it failed in my environment because no proxy was configured and my lab's firewall requires one. I used "dpkg-reconfigure" to configure a proxy, and the script then started the freshclam daemon automatically. However after it successfully ran, it still did not start clamd, noting that it failed to signal clamd in the logs because it was not running.

I'm not sure what the intended behaviour is. I was unable to check Debian's behaviour quickly because of bug 1590747. This needs following up.

Workaround: if you start clamav-freshclam manually, allow it to finish, then start clamav-daemon manually, I think everything will work from there on as normal.