I’m using avast! 4 for Linux in PCLinuxOS . I run it from a shortcut on my desktop , with /home/“user” permissions . Ran a Standard scan of my /home directory ; (I’m aware to scan the root file system I’d have to use Konsole as root ), and when scan completes there’s a list of files , and their paths . I left click a item to highlight it , then right click for options , which appear “Delete” , “Move to Chest” etc , and then get the message , “An error occured in avast! engine: No such file or directory”
When I installed Avast! I downloaded the RPM package , and installed it through Synaptic . I felt this the easiest way being a newbie to Linux. That aside it surprises me that I get these results after scanning , as I’d expect them to be Viruses , rather than a list of legitimate files . This has occured several times ; “An error occured in avast! engine: No such file or directory”
Any ideas ? Thanks .
First I assume this is just a list of files that avast couldn’t scan (not that they are infected or suspect), besides the file name and location (examples would help) there should be a reason why they can’t be scanned. You need to determine if the fie name, location and reason is likely to be a good reason.
Basically you shouldn’t touch these files or take any action as they are just files that avast couldn’t scan, not that they are infected or suspect. The same reason why they couldn’t be scanned is likely to be the same for being unable to take and selected option so you just further complicate the issue.
Abraxas, could only be reading access permission denied?
Also, which are your avat report settings?
I get the same result (list of all files and “An error occured in avast! engine: No such file or directory” message upon right-clicking an individual file) but only after doing a quick scan. It doesn’t matter if I’m doing a /home scan or a scan of my Windows’ partition.
By the way, there’s a spelling mistake in the error message: occurred is the correct spelling.
FreewheelinFrank:
I get the same result (list of all files and "An error occured in avast! engine: No such file or directory" message upon right-clicking an individual file) but only after doing a [u]quick scan[/u]. It doesn't matter if I'm doing a /home scan or a scan of my Windows' partition.Same as you say Frank , parameters: a "quick scan" , of [u]/home[/u] partition . I have noticed is the desktop shortcut I made runs Avast! with only user limited permissions . I can change that , but I think I'll just use a Terminal , and run Avast! scans as root . Not logon as root , but change Avast! permission to root. To run a scan using root permissions I opened a Terminal and ran: [me@localhost ~]$ su Password: [root@localhost me]# cd /bin [root@localhost bin]# avastgui This gave fewer "Permission denied" , "File was not tested due to configuration details " , "No such file or directory " in the scan results list . Although still get ; "An error occured in avast! engine: No such file or directory" upon right-clicking on an individual file within scan result list. Tech:
Abraxas, could only be reading access permission denied?Yes Tech , It seems scan results list are related to user permissions . But something more than a permission issue is going on , as you can see from running Avast! as both user and root . Plus that both FreewheelinFrank and myself get the same message . I wouldn't delete or move to virus chest any such files , as it's obviously an error .
Also, which are your avat report settings?In the Log viewer they ( the scan results ) are listed under ERROR . I'll check this out further to gain a better understanding of running scans so I can give more informed results . I guess the bottom line is Avast! struggles to scan certain Linux files . FreewheelinFrank :
By the way, there's a spelling mistake in the error message: occurred is the correct spelling.;D
This gave fewer "Permission denied" , "File was not tested due to configuration details " , "No such file or directory " in the scan results list . Although still get ; "An error occured in avast! engine: No such file or directory" upon right-clicking on an individual file within scan result list.
The problem seems to be with quick scan: I’d stick to standard scan- it doesn’t seem to take much longer.
By the way, there's a spelling mistake in the error message: occurred is the correct spelling. ;D
That was aimed at avast! the spelling mistake is real in the error notification.
The problem seems to be with quick scan: I'd stick to standard scan- it doesn't seem to take much longer.Thanks Frank , will try standard scan then.
"... the spelling mistake is real in the error notification."Yeah , I noticed it to , just reiterating the point , Cheers !
I’ll take to test later… now I’m on Vista.
But the Frank’s clue about the quick scanning could say something to the programmers…