I have two computers with Arch Linux and same systemd version (216) and /dev/fuse has different permissions on them after boot. One is my old laptop, /dev/fuse is 666 here. So I can use sshfs etc. with every user. The other is a newer desktop, and /dev/fuse got 600 permission. systemctl --version gives: systemd 216 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN My investigation: I see that here is an udev rule in systemd with chmod=0666 in '50-udev-default.rules', and indeed running on the new computer: udevadm trigger -c add -y 'fuse' fixes the permission to 666. The /dev/fuse file is created by 'systemd-tmpfiles-setup-dev.service' with 600 permission ('kmod-static-nodes.service' generates the tmpfiles.d config in '/run/tmpfiles.d/kmod.conf') I guess it's something with the 'systemd-udev-trigger.service' and the 'systemd-tmpfiles-setup-dev.service' starting simultaneously.
Creating a .conf file with [Unit] Before=systemd-udev-trigger in systemd-tmpfiles-setup-dev.d solves it.
Thanks for the report. I must admit that I don't see what the problem might be. May I ask you to set udev_log="debug" in /etc/udev/udev.conf and post the result both with a succeeding and a failing boot?
I can't reproduce it anymore. Sorry, maybe I was wrong about blaming systemd.
Ok, no problem. Please reopen if the problem reappears.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.