Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 2663 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

    I just had the same problem and tracked it down. You need to exlcude /opt/google/chrome in order to work around the issue.

    To do so:

    1) Enable the Sophos GUI if it not already enabled (run /opt/sophos-av/bin/savsetup and follow instructions)

    2) Go to http://localhost:8081

    3) Go to the Exclusions tab and enter /opt/google/chrome into the 'Files or directories (with or without wildcards)' box Some further details.

    if you are interested:

    The on-access scanner is having some unknown issue with the chrome binary: /opt/google/chrome/chrome. This can be confirmed by running a simple md5 command on the binary and then looking at dmesg output.

    (root) $ md5sum /opt/google/chrome/chrome md5sum: /opt/google/chrome/chrome: Timer expired

    (root) $ dmesg ... [ XXXX.XXXXXX] talpa-deny: Timeout occured while opening /opt/google/chrome/chrome on behalf of process md5sum[3041/3041] owned by 0(0)/0(0) <0>

    Hope This Helps

    :8981
Reply
  • 0

    I just had the same problem and tracked it down. You need to exlcude /opt/google/chrome in order to work around the issue.

    To do so:

    1) Enable the Sophos GUI if it not already enabled (run /opt/sophos-av/bin/savsetup and follow instructions)

    2) Go to http://localhost:8081

    3) Go to the Exclusions tab and enter /opt/google/chrome into the 'Files or directories (with or without wildcards)' box Some further details.

    if you are interested:

    The on-access scanner is having some unknown issue with the chrome binary: /opt/google/chrome/chrome. This can be confirmed by running a simple md5 command on the binary and then looking at dmesg output.

    (root) $ md5sum /opt/google/chrome/chrome md5sum: /opt/google/chrome/chrome: Timer expired

    (root) $ dmesg ... [ XXXX.XXXXXX] talpa-deny: Timeout occured while opening /opt/google/chrome/chrome on behalf of process md5sum[3041/3041] owned by 0(0)/0(0) <0>

    Hope This Helps

    :8981
Children
No Data
Unfiltered HTML