Your pacman log and journalctl might give some clues.
I guess he meant more or less complete logs. Give a journalctl log of a boot where you had the issue together with a pacman log including your latest updates (maybe since the problem began/ reappeared together with exact dates)
In 'journalctl -e' I see these lines: jan 30 11:00:58 csparch org.a11y.Bus[4553]: Activating service name='org.a11y.atspi.Registry' jan 30 11:00:58 csparch org.a11y.Bus[4553]: Successfully activated service 'org.a11y.atspi.Registry' jan 30 11:00:58 csparch org.a11y.atspi.Registry[4719]: SpiRegistry daemon is running with well-known name - org.a11y..atspi.Registry
Are these lines all right?
Looks to be part of https://www.archlinux.org/packages/extra/i686/at-spi2-core/ so yes seems to be all right
I suspect I have a virus mybe.
You do know you are using linux and the probability you do have one is through the sky?
So I just installed clamav but when I'm trying to start it with:
'sudo systemctl start clamd.service'
I get: Job for clamd.service failed. See "systemctl status clamd.service" and "journalctl -xe" for details.
'systemctl status clamd.service' clamd.service - clamav daemon Loaded: loaded (/usr/lib/systemd/system/clamd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since p 2015-01-30 21:14:04 CET; 10s ago Process: 9693 ExecStart=/usr/bin/clamd (code=exited, status=1/FAILURE)
It tells you to look in the logs. Did you do that?! Without wanting to be condescending: I don't think you should be using archlinux if you are not capable of looking through logs and searching google (I found the package for your "error" through a fast google search....)