ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!)

Bug #1925182 reported by Marius Gedminas
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clamav (Ubuntu)
Fix Released
Undecided
Lena Voytek
Bionic
Fix Released
Undecided
Lena Voytek
Focal
Fix Released
Undecided
Lena Voytek
Hirsute
Fix Released
Undecided
Lena Voytek
Impish
Fix Released
Undecided
Lena Voytek
Jammy
Fix Released
Undecided
Lena Voytek

Bug Description

[Impact]

When freshclam is enforced by apparmor in Bionic, and clamav packages are updated, the freshclam daemon will fail to restart.

Adding this fix will allow the freshclam daemon to restart automatically without error after an update.

This is fixed by backporting a fix made in Debian version 0.101.1+dfsg-1 that modifies the post-installation process to deploy the freshclam apparmor profile before restarting the daemon.

[Test Plan]

# lxc launch images:ubuntu/bionic test-failure
# lxc exec test-failure bash

# apt update
# apt dist-upgrade
# apt install -y apparmor apparmor-utils wget software-properties-common

- Install clamav packages of version 1 before current in bionic

# wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-freshclam_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-milter_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-testfiles_0.102.4+dfsg-0ubuntu0.18.04.1_all.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamdscan_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/libclamav-dev_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/libclamav9_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-daemon_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-docs_0.102.4+dfsg-0ubuntu0.18.04.1_all.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-base_0.102.4+dfsg-0ubuntu0.18.04.1_all.deb
# apt install -y ./*

- enforce apparmor profile for freshclam

# aa-enforce /usr/bin/freshclam

# apt update
# apt upgrade

- Check status of freshclam and notice that it was unable to restart

# systemctl status clamav-freshclam

● clamav-freshclam.service - ClamAV virus database updater
   Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/system/clamav-freshclam.service.d
           └─zzz-lxc-service.conf
   Active: failed (Result: exit-code) since Mon 2021-11-15 20:48:40 UTC; 34s ago
     Docs: man:freshclam(1)
           man:freshclam.conf(5)
           https://www.clamav.net/documents
 Main PID: 8785 (code=exited, status=2)

Nov 15 20:48:40 test-failure systemd[1]: Started ClamAV virus database updater.
Nov 15 20:48:40 test-failure freshclam[8785]: WARNING: Ignoring deprecated option SafeBrowsing at /etc/clamav/freshclam.conf:22
Nov 15 20:48:40 test-failure freshclam[8785]: ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
Nov 15 20:48:40 test-failure freshclam[8785]: ERROR: initialize: libfreshclam init failed.
Nov 15 20:48:40 test-failure freshclam[8785]: ERROR: Initialization error!
Nov 15 20:48:40 test-failure freshclam[8785]: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!).
Nov 15 20:48:40 test-failure systemd[1]: clamav-freshclam.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 15 20:48:40 test-failure systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'.

[Where problems could occur]

This change contains only part of the commit it is derived from, excluding other items like the 0.101.1 import and openssl apparmor profile modifications.

Since this portion has not yet been released on its own, new problems could arise from the exclusion of the unrelated changes.

Testers should watch for misbehaviors in the apparmor profile with this change. Error messages are often logged to the journal and can be seen by running "journalctl -fk"

[Original Description]

An unattended upgrade upgraded clamav last night, after which clamav-freshclam failed to start:

# systemctl status clamav-freshclam
● clamav-freshclam.service - ClamAV virus database updater
   Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2021-04-20 06:59:59 EEST; 6h ago
     Docs: man:freshclam(1)
           man:freshclam.conf(5)
           https://www.clamav.net/documents
 Main PID: 18433 (code=exited, status=2)

Apr 20 06:59:59 fridge systemd[1]: Started ClamAV virus database updater.
Apr 20 06:59:59 fridge freshclam[18433]: WARNING: Ignoring deprecated option SafeBrowsing at /etc/clamav/freshclam.conf:22
Apr 20 06:59:59 fridge freshclam[18433]: ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
Apr 20 06:59:59 fridge freshclam[18433]: ERROR: initialize: libfreshclam init failed.
Apr 20 06:59:59 fridge freshclam[18433]: ERROR: Initialization error!
Apr 20 06:59:59 fridge freshclam[18433]: ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!).
Apr 20 06:59:59 fridge systemd[1]: clamav-freshclam.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 20 06:59:59 fridge systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'.

The permissions of /var/log/clamav/freshclam.log are 0640 clamav:adm; the parent directory is mode 0755 clamav:clamav.

Restarting the clamav-freshclam service makes the error go away.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: clamav-freshclam 0.103.2+dfsg-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
Date: Tue Apr 20 13:39:47 2021
ProcEnviron:
 LC_CTYPE=lt_LT.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: clamav
UpgradeStatus: Upgraded to bionic on 2019-09-11 (586 days ago)

Related branches

Revision history for this message
Marius Gedminas (mgedmin) wrote :
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thank you for taking the time to file a bug report.

So, I've spent some time trying to reproduce it here, but was unsuccessful. Here's what I tried:

- Create a Bionic LXD container.

- Grab the .deb files for the last-but-one clamav version that was available in Bionic. They can be found here (for amd64): https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559

- Install the files grabbed above. Verify that the "clamav-freshclam.service" is running.

- apt update && apt ugprade. This will upgrade all clamav packages.

- Verify that the "clamav-freshclam.service" is still running.

Given the unsuccessful attempt to reproduce the problem, I tried searching on the internet for similar reports. I've found some people saying that this scenario might happen when there is a freshclam process blocked, which would prevent the new freshclam process (being started by systemd) from manipulating the log file. I don't know if that's your case, though, because I don't see any explicit error messages saying that there is another blocked freshclam process.

I have found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974, which, albeit similar, ended up being an apparmor problem that is not present in Ubuntu. I have also double checked your configuration files, and they both seem normal.

I'm wondering if this is a problem that happened due to very specific conditions: freshclam must have been busy trying to update the database, and coincidentally unattended-upgrades ran at that very moment and tried to restart the service, leading to the error.

Woud you be able to provide a bit more information so that we can try to reproduce the problem determine what's causing it? For example, would you be able to downgrade your freshclam/clamav packages and then update them again? Also, is there anything interesting in journalctl that is worth mentioning here? Some explicit message about the file being locked by another freshclam process, for example?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

Changed in clamav (Ubuntu):
status: New → Incomplete
Revision history for this message
Simon Déziel (sdeziel) wrote :

@sergiodj, I was able to reproduce this in a container based on your instruction but by adding the apparmor package to the mix.

With Apparmor installed, after upgrading from 0.102.4+dfsg-0ubuntu0.18.04.1 -> 0.103.2+dfsg-0ubuntu0.18.04.1, I have this in "journalctl -fk":

Apr 21 20:56:57 bclam kernel: audit: type=1400 audit(1619038617.624:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/clamd" pid=1835 comm="apparmor_parser"
Apr 21 20:57:00 bclam kernel: audit: type=1400 audit(1619038620.980:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/freshclam" pid=1837 comm="apparmor_parser"
Apr 21 20:57:11 bclam kernel: audit: type=1400 audit(1619038631.016:4): apparmor="DENIED" operation="open" profile="/usr/bin/freshclam" name="/etc/ssl/openssl.cnf" pid=1840 comm="freshclam" requested_mask="r" denied_mask="r" fsuid=105 ouid=0
Apr 21 20:57:11 bclam kernel: audit: type=1400 audit(1619038631.048:5): apparmor="DENIED" operation="open" profile="/usr/bin/freshclam" name="/etc/ssl/openssl.cnf" pid=1840 comm="freshclam" requested_mask="r" denied_mask="r" fsuid=105 ouid=0
Apr 21 20:59:30 bclam kernel: audit: type=1400 audit(1619038770.363:6): apparmor="DENIED" operation="open" profile="/usr/bin/freshclam" name="/etc/ssl/openssl.cnf" pid=1870 comm="freshclam" requested_mask="r" denied_mask="r" fsuid=105 ouid=0
Apr 21 21:04:37 bclam kernel: audit: type=1400 audit(1619039077.070:7): apparmor="DENIED" operation="open" profile="/usr/bin/freshclam" name="/etc/ssl/openssl.cnf" pid=2800 comm="freshclam" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Apr 21 21:04:37 bclam kernel: audit: type=1400 audit(1619039077.074:8): apparmor="DENIED" operation="capable" profile="/usr/bin/freshclam" pid=2800 comm="freshclam" capability=1 capname="dac_override"

The dac_override cap was added in the Apparmor profile shipped in 0.103.2+dfsg-0ubuntu0.18.04.1. It looks like the new profile is deployed after the freshclam service is restarted which would explain why it trips on the missing capability.

Manually restarting clamav-freshclam.service works around the problem.

Changed in clamav (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Marius Gedminas (mgedmin) wrote :

Thank you for the reproducer!

I was about to comment suggesting a race condition, since I have clamav-freshclam installed on several machines but only one of them reported a failure. Then I looked closer and realized that my monitoring is incomplete.

I have clamav-freshclam installed on two bionic and two focal servers. It failed to restart on both bionic servers (but only one of them was monitoring the presence of the freshclam process). Both focal servers are fine.

(This failure doesn't break the unattended upgrade -- dpkg thinks everything is fine. If I didn't have other monitoring set up, I would not have noticed that I'm not getting AV database updates, and the problem would self-correct after the next reboot.)

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Ah, thanks for the further investigation, Simon.

Indeed, I was able to reproduce the problem when using apparmor and verifying that /usr/bin/freshclam is confined.

I'm not sure if there's much we can do here; the best course of action for those experiencing this bug is to just restart the service, as the reporter himself mentioned.

I'm marking this bug as Triaged and subscribing ubuntu-server, anyway. Thank you both for confirming the bug.

Changed in clamav (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Simon Déziel (sdeziel) wrote :

I just took a closer look and the postinst is clearly wrong. The freshclam daemon is started before the profile is deployed:

cat /var/lib/dpkg/info/clamav-freshclam.postinst:
...
case "$1" in
  configure)
...

  if [ "$runas" = 'daemon' ]; then
    update-rc.d clamav-freshclam defaults >/dev/null
    invoke-rc.d clamav-freshclam start
  elif [ "$runas" = 'ifup.d' ]; then
...
  fi
  ;;
  abort-upgrade|abort-remove|abort-deconfigure)
  ;;
  *)
  echo "postinst called with unknown argument \`$1'" >&2
  exit 1
  ;;
esac

# AppArmor integration
if [ "$1" = "configure" ]; then
    APP_PROFILE=/etc/apparmor.d/usr.bin.freshclam
    if [ -f "$APP_PROFILE" ]; then
        # Add the local/ include
        LOCAL_APP_PROFILE=/etc/apparmor.d/local/usr.bin.freshclam

        test -e "$LOCAL_APP_PROFILE" || {
            tmp=`mktemp`
        cat <<EOM > "$tmp"
# Site-specific additions and overrides for usr.bin.freshclam.
# For more details, please see /etc/apparmor.d/local/README.
EOM
            mkdir `dirname $LOCAL_APP_PROFILE` 2>/dev/null || true
            mv -f "$tmp" "$LOCAL_APP_PROFILE"
            chmod 644 "$LOCAL_APP_PROFILE"
        }

        # Reload the profile, including any abstraction updates
        if aa-status --enabled 2>/dev/null; then
            apparmor_parser -r -T -W "$APP_PROFILE" || true
        fi
    fi
fi
...

So post-installation, freshclam runs unconfined:

root@bclam:~# aa-status
apparmor module is loaded.
6 profiles are loaded.
6 profiles are in enforce mode.
   /sbin/dhclient
   /usr/bin/freshclam
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/sbin/clamd
0 profiles are in complain mode.
1 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
1 processes are unconfined but have a profile defined.
   /usr/bin/freshclam (823)

That's something that is better fixed in Debian. I'll try to send a merge request through Salsa.

Revision history for this message
Simon Déziel (sdeziel) wrote :
Bryce Harrington (bryce)
Changed in clamav (Ubuntu Bionic):
status: New → Triaged
Bryce Harrington (bryce)
tags: added: server-next
Bryce Harrington (bryce)
Changed in clamav (Ubuntu):
assignee: nobody → Bryce Harrington (bryce)
Bryce Harrington (bryce)
Changed in clamav (Ubuntu Bionic):
assignee: nobody → Bryce Harrington (bryce)
Bryce Harrington (bryce)
Changed in clamav (Ubuntu Focal):
status: New → Triaged
Changed in clamav (Ubuntu Hirsute):
status: New → Triaged
assignee: nobody → Bryce Harrington (bryce)
Changed in clamav (Ubuntu Focal):
assignee: nobody → Bryce Harrington (bryce)
Lena Voytek (lvoytek)
Changed in clamav (Ubuntu):
assignee: Bryce Harrington (bryce) → Lena Voytek (lvoytek)
Changed in clamav (Ubuntu Focal):
assignee: Bryce Harrington (bryce) → Lena Voytek (lvoytek)
Lena Voytek (lvoytek)
Changed in clamav (Ubuntu Bionic):
assignee: Bryce Harrington (bryce) → Lena Voytek (lvoytek)
Changed in clamav (Ubuntu Hirsute):
assignee: Bryce Harrington (bryce) → Lena Voytek (lvoytek)
Changed in clamav (Ubuntu Impish):
assignee: Bryce Harrington (bryce) → Lena Voytek (lvoytek)
Changed in clamav (Ubuntu Bionic):
status: Triaged → In Progress
Lena Voytek (lvoytek)
Changed in clamav (Ubuntu Jammy):
status: Triaged → In Progress
Lena Voytek (lvoytek)
description: updated
Revision history for this message
Lena Voytek (lvoytek) wrote :

confirmed this has been fixed for all releases after Bionic

Changed in clamav (Ubuntu Focal):
status: Triaged → Fix Released
Changed in clamav (Ubuntu Hirsute):
status: Triaged → Fix Released
Changed in clamav (Ubuntu Impish):
status: Triaged → Fix Released
Changed in clamav (Ubuntu Jammy):
status: In Progress → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Marius, or anyone else affected,

Accepted clamav into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/clamav/0.103.2+dfsg-0ubuntu0.18.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in clamav (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Lena Voytek (lvoytek) wrote :
Download full text (3.3 KiB)

Verified proposed version is working properly with the following

# lxc launch images:ubuntu/bionic test-success
# lxc exec test-success bash

# apt update && apt dist-upgrade -y
# apt install -y apparmor apparmor-utils wget

- Install clamav packages of version 1 before current in bionic

# wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-freshclam_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-milter_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-testfiles_0.102.4+dfsg-0ubuntu0.18.04.1_all.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamdscan_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/libclamav-dev_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/libclamav9_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-daemon_0.102.4+dfsg-0ubuntu0.18.04.1_amd64.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-docs_0.102.4+dfsg-0ubuntu0.18.04.1_all.deb https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/19629559/+files/clamav-base_0.102.4+dfsg-0ubuntu0.18.04.1_all.deb
# apt install -y ./*

- enforce apparmor profile for freshclam

# aa-enforce /usr/bin/freshclam

- Enable proposed and update to proposed version

# cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main
EOF

# apt update && apt upgrade -y

- Check status of freshclam and notice that it now starts properly

# systemctl status clamav-freshclam

● clamav-freshclam.service - ClamAV virus database updater
   Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/system/clamav-freshclam.service.d
           └─zzz-lxc-service.conf
   Active: active (running) since Wed 2022-01-12 17:44:12 UTC; 33s ago
     Docs: man:freshclam(1)
           man:freshclam.conf(5)
           https://www.clamav.net/documents
 Main PID: 9765 (freshclam)
    Tasks: 1 (limit: 19005)
   CGroup: /system.slice/clamav-freshclam.service
           └─9765 /usr/bin/freshclam -d --foreground=true

Jan 12 17:44:12 test-success freshclam[9765]: Wed Jan 12 17:44:12 2022 -> ^Local version: 0.103.2 Recommended version: 0.103.5
Jan 12 17:44:12 test-success freshclam[9765]: Wed Jan 12 17:44:12 2022 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
Jan 12 17:44:12 test-success freshclam[9765]: Wed Jan 12 17:44:12 2022 -> daily.cvd database is up-to-date (version: 26420, sigs: 1970864, f-level: 90, builder: raynman)
Jan 12 17:44:12 test-success freshclam[9765]: Wed Jan 12 17:44:12 2022 -> main.cvd database is up-to-date (version: 62, sigs: 66474...

Read more...

tags: added: verification-done-bionic
removed: verification-needed-bionic
tags: added: verification-done
removed: verification-needed
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for clamav has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package clamav - 0.103.2+dfsg-0ubuntu0.18.04.3

---------------
clamav (0.103.2+dfsg-0ubuntu0.18.04.3) bionic; urgency=medium

  * Deploy apparmor profile before first start of freshclam daemon.
    - d/control: Add dh-apparmor as a build dependency
    - d/rules: Add dh install override to deploy apparmor profiles
    - d/clamav-daemon.postinst.in: Remove old apparmor profile deployment
    - d/clamav-freshclam.postinst.in: Remove old apparmor profile deployment
    Thanks to Sebastian Andrzej Siewior <email address hidden>.
    (LP: #1925182)

 -- Lena Voytek <email address hidden> Mon, 29 Nov 2021 10:13:20 -0700

Changed in clamav (Ubuntu Bionic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.