tl;dr When I turn on user_allow_other in /etc/fuse.conf in Fedora Linux 43, the suspend feature stops working.

Background

I wanted to create a Samba share below a gocryptfs mount point. Since I ran into an access permissions problem when I tried that and that gocryptfs uses FUSE, I figured that I had to enable user_allow_other in FUSE and add the -allow_other option when starting gocryptfs.

In the end, this idea did not solve the access problem. But that's also when I ran into the suspend problem.

Discussion

The way the suspend feature broke after enabling user_allow_other is itself weird. It only freezes the system the second time I try to suspend it. The first suspend and wake up work fine. The freeze only happens on the second suspend.

I have no idea how a FUSE setting can affect power management. When transitioning the system to suspend state, does systemd somehow touch a userspace filesystem? This issue will be difficult and annoying to debug because I have to reboot the laptop every time it freezes on suspend.