ClamTk

2. Do you speak more than one language? See the Launchpad page. The easiest way to install clamtk is to use the rpms. The commands dnf and yum will pull in requirements. If this does not work, download the file from the official site. You should be able to just double click the file for installation or upgrade. For these examples, we will use version 6.17. The name of the file may differ based on your distribution. Warning : Don't do this. It's much easier to just double click a .deb or .rpm. Really, put down the source. If you have installed this program as an rpm or .deb, you do not need to take these steps. Did you get errors with this? Check the TROUBLESHOOTING section at the end. You should be able to just double click the .deb file to install it. Your package manager should retrieve any necessary dependencies. It is recommended you install clamtk from official repositories. Check your distribution first, and always install from trusted sources. While the Debian/Ubuntu .debs used to be digitally signed, they are not anymore; the way I used to do that no longer works. The rpms are digitally signed. Here's how you can verify the rpms: 1. Get and import the key in one step: rpm --import 2. Verify the list of gpg keys installed in RPM DB: rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} -- %{summary} n' 3. Check the signature of the rpm. For this example, we'll use version 6.17: rpm --checksig clamtk-6.17-1.fc39.noarch.rpm 4. You should see something like this: /home/you/clamtk-6.17-1.fc39.noarch.rpm: rsa sha1 (md5) pgp md5 OK You can also verify the tarball. Using 6.17 as the example version, ensure you have downloaded the tarball, its detached signature (.asc), and the key in step 1 above. 1. Get the key (skip this step if you already have it): wget 2. Import it (skip this step if you have done it already): gpg --import RPM-GPG-KEY-DaveM-20230506 3. Verify like so: gpg2 --verify clamtk-6.17.tar.xz.asc clamtk-6.17.tar.gz or gpg --verify clamtk-6.17.tar.xz.asc clamtk-6.17.tar.xz 4. You should see something like this: gpg: Signature made Sun 11 Sep 2016 06:29:41 AM CDT using RSA key ID (snipped for brevity). Then you will need the minisig file for the program you are verifying. The main reason for the commandline option (however basic) is to allow for right-click scanning within your file manager (e.g., Files, Caja, or Dolphin). If you require more extensive commandline options, it is recommended that you use the clamscan executable itself. (Type man clamscan at the commandline.) You can view and delete scan logs by selecting the "History" option. You also have a few options with the files displayed. Click on the file scanned to select it, then right-click: you should have four options there. If you've quarantined files for later examination, you have the option to restore them to their previous location (if known), or delete them. Here are the specific pages. Note that these are mirrored on Github as well. You probably have more than one virus signature directory. See below answer for finding signatures. clamtk is trying to find its virus definitions. Typically these are held under /var/lib/clamav or /var/clamav or somewhere else. If you are sure these files exist, please find their location and send it. Try the following to determine their location: 1. find /var -name "daily.cvd" -print 2. find /var -name "daily.cld" -print Are you using the source and you see something like this: Can't locate Foo/Bar.pm in @INC. (etc, etc). This means you are missing some of the dependencies. Try to find the dependency through your distribution's repositories, or simply go to CPAN. Always try your distribution's repository first. It is more than likely your distribution already packages these for easy installation. Depending on your distro, you will likely use yum , dnf , apt or some "Update Manager" and the like. That's because we no longer bundle this functionality. Not everyone uses Gnome. There are add-ons fo