> Having said that, since it's just a warning for clamav and doesn't
cause a functional problem, I'm not sure an SRU would be justified.

To re-iterate: this is fixed in Bionic. It still affects Xenial, but
unless there's a functional reason this is a problem for users, rather
than just a log message, I see no need to fix this in Xenial. If anyone
has a justification, please comment.

** Changed in: clamav (Ubuntu Xenial)
       Status: New => Won't Fix

** Tags removed: bitesize server-next

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  apparmor regression blocking freshclam process info

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to