I’ve been using Avast! 1.3 Home Edition for Ubuntu 10.04 64-bit for weeks now and had no trouble with virus definition updates until today. I get the corrupt download update repeatedly. Is anyone else getting this? My rcS file is still in /etc/init.d.
** Update **
Okay. Problem appears to be solved. Thanks to zilog for leading me in the right direction by suggesting the vps was being truncated. As I mentioned, the corrupted updates started occurring when I installed Privoxy, which is a proxy server with built-in adblock filtering. I use Google Chrome as my primary browser. In the Chrome proxy settings, I opted to apply the changes system-wide…This modified the gconf settings, applying the new proxy setting to package installs (and probably avast! vps updates). As soon as I changed system-wide settings back to direct-connect (and rebooted), the avast! update problems went away.
59 views and no replys. I guess I’m the only one and I’m on my own. In the same day the corruption messages appeared, I installed Privoxy along with several package updates from the main repositories. There’s no telling if one of those broke avast! I’ll have to re-install avast! from the debian package. If that doesn’t work, I’ll have to switch to a different virus scanner. Avira Antivirus never gave me problems on MS Windows.
Hallo,
just download the 400.vps, and compare with its 400vps.md5 (both files are online aqt http://files.avast.com/files/latest/). probaqbly, something is truncating your file.
Thanks but your link appears to be broken. Page not found. I did some further searching and haven’t found a direct download link from the website for virus definitions.
Something is truncating my file? I’m not running the vps-update through Privoxy, unless avast relies on my browser proxy settings. Even so, I don’t think Privoxy would touch virus definition files.
update
I managed to successfully update the database from avast! in 1 out of 11 tries. Corrupt update files are still an issue.
Okay. Problem appears to be solved. Thanks, zilog for leading me in the right direction by suggesting the vps was being truncated. As I mentioned, the corrupted updates started occurring when I installed Privoxy, which is a proxy server with built-in adblock filtering. I use Google Chrome as my primary browser. In the Chrome proxy settings, I opted to apply the changes system-wide…This modified the gconf settings, applying the new proxy setting to package installs (and probably avast! vps updates). As soon as I changed system-wide settings back to direct-connect (and rebooted), the avast! update problems went away.