Hello,
My system works fine with systemd-228-15.2. After upgrading to 228-16 (with systemd-sysvinit udev) the journal contains entries like:
cron[16200]: pam_systemd(crond:session): Failed to connect to system bus: No such file or directory dbus[1257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out sddm-helper[16255]: pam_systemd(sddm:session): Failed to connect to system bus: No such file or directory
A reboot results in several failed services (avahi, bluetooth, ModemManager, login-systemd, NetworkManager) , as far as I can see due to dbus access failure. Other programs, e.g. gpg (failed IPC call), are affected, too.
systemd-logind[1254]: Failed to connect to system bus: No such file or directory dbus[1257]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed outdbus[1257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out dbus[1257]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out dbus[1257]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
How to analyze that?
Greetings mab
KDE-Plasma-Version: 5.8.4 KDE-Frameworks-Version: 5.28.0 Qt-Version: 5.7.0 Kernel-Version: 4.8.10-1-default
This was caused by a separately mounted tmpfs on /var/run ; in consequence there was no /var/run/dbus.