Strange report on Ubuntu 9.10

Avast Business Avast Business for Linux
1

Hi,
Today I’ve installed Ubuntu 9.10 (thanks to wubi.exe) on Windows XP Home machine. And on Ubuntu I’ve installed avast! Linux Home Edition version 1.3.0. After home folder scan, I’ve checked scan report and I saw this:

  • avast! Report
  • This file is generated automatically
  • Started on pon, 28 gru 2009, 16:32:44
  • VPS: 91227-1, 27.12.2009

Infected files: 450971566080
Total files: 450971575830
Total folders: 450971566541
Total size: 929,3 MiB

  • Stopped on pon, 28 gru 2009, 16:33:05
  • Runtime was 00:00:21

How to explain this? ???

2

For sure, makes no sense Infected files: 450971566080
I have Kubuntu 9.10 installed over Vista and never got such a report…

3

Some people reported similar problem with previous build, and reporting, that with this current one the problem is gone. Does pure avast (not avastgui) report the same, in this case? What version (32bit/64bit) do you use?

regards,
pc

4
Does pure avast (not avastgui) report the same
No, report from Avast launched in terminal is correct.
What version (32bit/64bit) do you use?
I'm using 32bit version.
5

try to edit that /usr/bin/avast script - there’s a FAILSAFE option, which will force the app to use its bundled libraries (and not those system ones, from your distro). Might help, let me know whether it solved this flaw.

regards,
pc

6
try to edit that /usr/bin/avast script
What do I have to change in this file?

#if test uname -m = “x86_64” ; then

# use all included libraries when running on 64bit platform

AVAST_FAILSAFE=1

#fi

I’ve removed these hash marks (marked red), but this didn’t help.

7

Hallo,
just move the AVAST_FAILSAFE=1 line below the #fi (to be executed unconditionally upon each startup). Of course, on your IA-32, the condition was always false and thus not helpful.

regards,
pc

8
just move the AVAST_FAILSAFE=1 line below the #fi
Only gui has changed. Report does not.
9

strange. this bug isn’t reproducible in a deterministic manner, so it’s hard to catch it. seems like the internal counters in the engine aren’t initialised properly, but:

these are the same, as in non-gui version of avast (type: avast <some_path> - will the report at the end contain this flaw too?)

regards,
pc

10
type: avast - will the report at the end contain this flaw too?
Reports from Avast launched in terminal are correct.
11

So, we can suspect wx wigets that some constructor isn’t under some circumstances called… hmm.
Unfortunately, this flaw is not reproducible on my machine.

regards,
pc