Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 2665 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Chrome won't start. Sophos AV 7.2.2 under Ubuntu 10.04

Warren

I just installed Sophos AV 7.2.2 on my laptop running Ubuntu 10.04 and for some reason the chrome browser won't start anymore.  When I run chrome and check my system stats I can see the process savscand using 90% of my cpu.  After a while that process goes away and nothing further happens.  The sophos log reads:

savd.scanner.died Force-terminated a scan processor.

When I disable on-access scanning, I can run chrome again without problems.  The firefox browser starts without problems with on-access scanning enabled.  Does anybody have an idea how I can solve this issue (short of disabling on-access scanning of course)?

:7035


This thread was automatically locked due to age.
Parents
  • 0

    The log message and CPU usage suggest that a scanner has got stuck scanning some file.

    Since we'd probably have more reports of problems if it was with the binaries of Chrome, it's most likely in the cache/user files on your home directory.

    You might be able to spot the file(s) taking a long time to scan with a savscan command:

    savscan -dn ~/.config/chromium ~/.cache/chromium

    Otherwise using exclusions you can see which files cause the problem with binary chop. Alternatively there is a procedure using Talpa debugging to see which files are being scanned, but it's quite complicated.

    Once you know the files, you can either exclude them, or report them as problem files to Sophos, so that we can work out why they are taking so long to scan.

    :7067
Reply
  • 0

    The log message and CPU usage suggest that a scanner has got stuck scanning some file.

    Since we'd probably have more reports of problems if it was with the binaries of Chrome, it's most likely in the cache/user files on your home directory.

    You might be able to spot the file(s) taking a long time to scan with a savscan command:

    savscan -dn ~/.config/chromium ~/.cache/chromium

    Otherwise using exclusions you can see which files cause the problem with binary chop. Alternatively there is a procedure using Talpa debugging to see which files are being scanned, but it's quite complicated.

    Once you know the files, you can either exclude them, or report them as problem files to Sophos, so that we can work out why they are taking so long to scan.

    :7067
Children
No Data
Unfiltered HTML