This may be redundant as I haven't read the entire comment thread, but the issue is that logwatch relies on log entries like ``` ClamAV update process started at Fri Nov 6 10:07:41 2026 ``` rather than the timestamps to determine the times of entries. freshclam 1.5.4+dfsg-0ubuntu0.22.04.1 doesn't write those log entries although freshclam 1.5.4+dfsg-0ubuntu0.26.04.1 does write them. So the issue is fixed in Ubuntu 26.04, but not in 22.04.
The attached clam.patch will change the logwatch script to use the log entry timestamps instead of the `ClamAV update process started` header. ** Patch added: "clam.patch" https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/2067608/+attachment/6015529/+files/clam.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067608 Title: clamav-freshclam 1.0.5 and logwatch 7.7-1 fails to report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2067608/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
