Dave M

That does seem pretty slow - over 30 seconds for one file. I did a scan of one file: clamscan -r ~/tmp/ LibClamAV Warning: ************************************************** LibClamAV Warning: *** The virus...

I don't know if I'd recommend removing signatures as the solution... I'll keep thinking on it.

Temporarily moving them out sounds like a good test.

Yes, I've seen this too. Not sure yet what causes it.

Hi @CodingSpiderFox , Check out this clamav page: http://www.clamav.net/contact . There is a link specifically for reporting false positives. Maybe just a button that allows for submission to this would...

Hi, Please open a terminal window and type the following: cat ~/.clamtk/restore Mine looks like this: $ cat .clamtk/restore 06f2c2aade7582da82a9b7469eca506d11858dfa10b2491f6fab88a13f33f8ec:/home/dave/test/CVE-2015-1641.gz:664 3ba2e5b32124c208bc1d10e4ea6685b243d98298e0594f93fad6e36b70fa35e9:/home/dave/test/pkg.7z:664 Let's see how they're getting stored for either removal...

Hi @Lehmeiers , Do you mean signature updates? If so, please update to version 6.09. https://github.com/dave-theunsub/clamtk/releases/tag/v6.09 respectfully, Dave M

Hi @Lehmeiers , Thank you for reporting the issue and following up. Please keep us up to date and let us know if we can help. respectfully, Dave M

Hi @Lehmeiers , How are you updating manually? Also, what is the output of `grep Update ~/.clamtk/prefs`? respectfully, Dave M

Hi @Lehmeiers , Sorry for the delay. Please try this: open the Scheduler, remove the scheduled update, and re-add it. respectfully, Dave M