I’ve rebased from Aurora to Bazzite for one of machines and the user unit files in /var/home/mikael/.config/systemd/user/ wont work in Bazzite.
systemctl enable --now --user var-home-mikael-mnt-data01.mount gives Job failed. See “journalctl -xe” for details.
journalctl -xe says `jan 09 21:35:39 bazzite mount[205455]: mount: /var/home/mikael/mnt/data01: must be superuser to use mount.`
Why would a superuser be needed for a user unit file? Running as user worked fine in Aurora.
I don’t think you can do mounts as a user unit file by default.
You can, by default, in Aurora. If Bazzite is different, can I “change the default”?
Honestly, I’m not clear whether Aurora differs from Bazzite in a way that affects this, and I wouldn’t have expected them to be different. Everything I’ve seen indicates you generally can’t mount a traditional filesystem from a systemd user unit. It’s not “unit files” in general, it’s specifically .mount units: mounting typically requires elevated privileges which user services don’t have by default. For most filesystems, the normal pattern is to mount via a system-level unit (or another privileged mechanism) and then control user access via ownership/permissions (and, where applicable, mount options). Maybe somebody else will respond with more info. Its weird that it worked in Bazzite.