The thing is, I never installed comodo antivirus… There was no need for it. As far I know, it’s not in the system, because I can’t see anything related to “comodo”, nor “antivirus” on the installed packages list, and have no idea why this error showed up.
Then why journal logs show me this error?
systemd: Failed to start Comodo Antivirus
I know it’s a harmless error, but I would like to clean it up, if possible.
I going through possible paths and so far didn’t find anything related to comodo or antivirus. However, I noticed:
I uninstalled foldingathome app 2 years ago, so why there is still systemd unit for it? Can I safely remove it by removing the folder? Or maybe will it break something, because the path to that folder is somewhere else as well?
It’s anyway inactive and dead.
So basically, how to remove it safely? I bet that the answer is somewhere in this article. I recall deleting some systemd services in the past, but I don’t recall details, so I prefer to ask, if you know the answer from the top of your head.
That is actually a directory and not a system unit on it’s own.
Directories like that (ending in .d are used to place “drop-in” files to override settings of the unit file (without the .d extension)
So if there is no foldingathome.service anywhere in your system, you could safely remove that directory and it’s contents if you’re sure you won’t be needing it again in future…
To make sure you can use one of or both of:
systemctl status foldingathome
systemctl cat foldingathome This last one will show all files involved with that unit.
Make sure to grep for that text inside the unit files, and not just look at filenames…
Also, the folder is not empty. It contains override.conf
However, I’m sure I won’t be needing it. This was clearly automatically added by foldingathome app, or maybe it was added manually after following install instruction? I don’t recall that now. This isn’t needed by anything else on the computer and is specific to that app, which I won’t be using anyway.
More close on-topic, Plasma doesn’t see any unit for comodo or antivirus. I also can’t find it, so I still don’t know where it is hidden.
Can it be, that the unit for comodo anitvirus doesn’t exist but is still requested by something else, hence the error?
I don’t speak polish so i can’t say what your screenshot shows.
But i do see the “not found” at start of that line, which is strange indeed…
Maybe it is tried to be pulled-in by some other unit’s dependency, system or user unit no idea…
Please also take note that the command line versions will show you the definitive answer, the GUI might be using an outdated cache
As i told in reply #2, that’s the only way to find which unit has “Comodo Antivirus” as description because that is used in the log line you mentioned…
Once you find that unit you can start checking the dependencies of said unit, to see who is interacting with it…
Maybe check the log lines before and after that log line you mentioned to see clues that are related to it…
Is it cap sensitive? I’m testing it on “fah” that I know it exists in this foldingathome service.
Different from “Comodo”, this time the search takes a long time to complete. I’m waiting for 2-3 mintues and it’s still running: