You are not logged in.
Hello,
on my Arch Linux system I'm experiencing a strange behavior where, after the installation of the system, I have correctly "bus=" file and "systemd" directory in "/run/user/1000", and, sometimes, after a reboot, they are missing. The missing of "bus" file does not allow me to call dbus correctly, while I guess that the missing of "systemd" directory does not allow me to run systemd services as the current user with UID=1000. I'm noting that systemd for root should work because by running "sudo systemctl status <servicename>" it works correctly.
$XDG_RUNTIME_DIR is correctly set to /run/user/1000
The content of "/etc/pam.d/system-login" is:
#%PAM-1.0
auth required pam_shells.so
auth requisite pam_nologin.so
auth include system-auth
account required pam_access.so
account required pam_nologin.so
account include system-auth
password include system-auth
session optional pam_loginuid.so
session optional pam_keyinit.so force revoke
session include system-auth
session optional pam_motd.so
session optional pam_mail.so dir=/var/spool/mail standard quiet
-session optional pam_systemd.so
session required pam_env.so
What is the process or command that at boot should create "bus" and "systemd" in /run/user/1000?
If these two file/directory are missing after a reboot, is there a way to generate them manually by a command?
Last edited by D3vil0p3r (2023-04-05 20:30:26)
Offline
They are/should be created on login by pam_systemd, how or into what are you logging into?
Online
I solved it. user@1000 service failed to start. When I started it by "sudo systemctl start user@1000" and then "bus" and "systemd" appeared again.
Offline
And why did it fail?
sometimes, after a reboot, they are missing
Suggests that this will happen again and pot. is some race condition you want to address?
Offline