Hi Leonidas,
Can you please advise if ubuntu 16 will receive the patch in the future ?
As per the current status 'xenial' is marked as 'Fix released' but the issue is
persisting.
Regards.
** Changed in: clamav (Ubuntu Xenial)
Status: Fix Released => Incomplete
** Changed in: clamav
Hi,
Can you please advise if ubuntu 16 will receive the patch in the future ?
As per the current status 'xenial' is marked as 'Fix released'...
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@leosilvab
Is it possible to apply the fix for the ubuntu 16 (xenial) packages ?
Regards
sudo apt-get install --only-upgrade clamav clamav-base clamav-daemon
clamav-freshclam clamdscan libclamav9:amd64
Reading package lists... Done
Building dependency tree
Reading state information...
Hi Mark,
Please find below the output from clamconf -n
Indeed, I use ExcludePath in the configuration.
If I remove the ExcludePath(s) from the config, the scan starts with both
parameters (--fdpass & --multiscan )
Regards
Config file: clamd.conf
---
PreludeAnalyzerName =
Please find below some tests
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.10
DISTRIB_CODENAME=groovy
DISTRIB_DESCRIPTION="Ubuntu 20.10"
/etc/lsb-release (END)
root@hostname:/opt# /usr/bin/clamdscan --log=/var/log/clamav/clamav.log
--stdout --verbose --multiscan --fdpass /opt
On Ubuntu 20.04.2 LTS, downgraded to 0.102.2 - the issue does not occur
** Summary changed:
- clamdscan MULTISCAN Segmentation fault
+ clamdscan - MULTISCAN parameter causes Segmentation fault
** Summary changed:
- clamdscan - MULTISCAN parameter causes Segmentation fault
+ clamdscan -
Public bug reported:
While running clamdscan with the --multiscan parameter we get the
following error: Segmentation fault (core dumped)
The scan starts without '--multiscan' but it cause performance issues
The issue is present on Ubuntu 16.04.7 LTS, Ubuntu 18.04.5 LTS, Ubuntu 20.04.2
LTS
