Comment 3 for bug 258424

I was able to find out some more information about the problem I am having. I found that KlamAV modifies my crontab in order to run scheduled scans:

crontab:
...
# KlamAV Scheduled Scan of /home/chris/
0 12 * * * /home/chris/.klamav/ScanWithKlamav_130808141030.sh '/home/chris/'
# KlamAV Scheduled Scan of /home/chris/
40 13 * * * /home/chris/.klamav/ScanWithKlamav_190808133139.sh '/home/chris/'
...

If I run one of those tasks manually with KlamAV open, the task won't run and I get the following:

chris@chris-laptop:~$ /home/chris/.klamav/ScanWithKlamav_190808133139.sh '/home/chris/'
cat: /home/chris/.DCOPserver_:0: No such file or directory
object '/usr/bin/dcop' in application 'is' not accessible
object not accessible
chris@chris-laptop:~$

If I close KlamAV and try again, KlamAV opens and the scheduled scan begins. I still get some errors on the command line:

chris@chris-laptop:~$ /home/chris/.klamav/ScanWithKlamav_190808133139.sh '/home/chris/'
cat: /home/chris/.DCOPserver_:0: No such file or directory
object '/usr/bin/dcop' in application 'is' not accessible
object not accessible
kdecore (KProcess): WARNING: _attachPty() 19
kdecore (KProcess): WARNING: _attachPty() 21
LibClamAV Error: Database Directory: /var/lib/clamav not locked
QLayout "unnamed" added to Klamav "KlamAV ", which already has a layout
chris@chris-laptop:~$