Package Details: foldingathome 7.6.21-1

Git Clone URL: (read-only, click to copy)
Package Base: foldingathome
Description: A distributed computing project for simulating protein dynamics
Upstream URL:
Keywords: folding foldingathome
Licenses: custom
Submitter: dtw
Maintainer: rustymech
Last Packager: rustymech
Votes: 164
Popularity: 2.32
First Submitted: 2007-06-28 14:55
Last Updated: 2021-01-09 21:16

Pinned Comments

alucryd commented on 2020-04-21 14:23

To be clear, nvidia users need to enable both foldingathome.service and foldingathome-nvidia.service.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

merlock commented on 2020-08-27 02:15

I think you need to add


To the service file; otherwise the client logs to both /var/log/foldingathome/log.txt and the journal.

alucryd commented on 2020-05-26 17:48

@geripgeri Thought that directory existed even with no graphics card, made it optional.

geripgeri commented on 2020-05-21 06:45

Hey @jpkotta!

/dev/dri doesn't exist in my your system, /usr/bin/chown and /etc/foldingathome both exist.

After I added ReadWritePaths=-/dev/dri to foldingathome.service the service starts without any issue!

Thank you for your help!

jpkotta commented on 2020-05-20 20:59

@geripgeri: Does /dev/dri exist on your system? If not, try editing foldingathome.service to have ReadWritePaths=-/dev/dri (this should probably be changed in the package, you shouldn't need /dev/dri if you're doing CPU folding).

As for the chown, that doesn't make sense. Do /usr/bin/chown and /etc/foldingathome both exist?

geripgeri commented on 2020-05-18 13:03

Hey! I'm getting this error message: The system is up to date. I don't have GPU in this pc, FAH worked for me before.

systemd[1]: Starting Folding@home distributed computing client...
systemd[2846840]: foldingathome.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/dri: No such file or directory
systemd[2846840]: foldingathome.service: Failed at step NAMESPACE spawning /usr/bin/chown: No such file or directory
systemd[1]: foldingathome.service: Control process exited, code=exited, status=226/NAMESPACE
systemd[1]: foldingathome.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Folding@home distributed computing client

What could cause this issue?

katt commented on 2020-05-16 19:35

@alucryd: I realise I should've tried this before, either way it does not help. Moved back sleep to the main service and re-activated the nvidia one and I ended up having to run startx manually. (as wasn't active)

EDIT: It's now happening with only foldingathome.service, so I guess it's the sleep command then, but it used to work before? Computers yo...

alucryd commented on 2020-05-16 08:21

@katt: Can you try putting the sleep command back to the foldingathome.service unit?

katt commented on 2020-05-14 19:29

I've just discovered that with the foldingathome-nvidia service activated, stays "inactive (dead)" until I've logged out and back in. This causes problems such as xorg not autostarting (

This didn't happen a while back so possibly has something to do with the moved sleep command?

AntiComposite commented on 2020-05-09 15:15

Yes, fully updated. After a sudo useradd fah, the service starts fine.

Correction: I found an /etc/nsswitch.conf.pacnew. My existing /etc/nsswitch.conf didn't allow systemd to control users and groups. I fixed that, removed the manually-created user, and the service started normally.

alucryd commented on 2020-05-09 10:13

@AntiComposite: Those should be created automatically by systemd, and automatically deleted when the service exits. It's working fine here, is your system up to date? Can you try creating these manually?