You are not logged in.
After a recent update, I noticed this a few days ago so maybe on Friday, something changed that now causes my SystemD user session to fail. At the system level everything seems fine systemctl status doesn't report that there are any failed services
systemctl status
● Vili
State: running
Jobs: 0 queued
Failed: 0 units
Since: Mon 2017-06-12 19:13:06 EDT; 35min agobut if I run systemctl --user status I get the following error
systemctl --user status
Failed to connect to bus: No such file or directoryDbus is currently running so that probably isn't the "bus" that systemd --user fails to connect to
> systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
Active: active (running) since Mon 2017-06-12 19:13:09 EDT; 38min ago
Docs: man:dbus-daemon(1)
Main PID: 650 (dbus-daemon)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/dbus.service
└─650 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
Jun 12 19:20:39 Vili dbus[650]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
Jun 12 19:20:40 Vili dbus[650]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Jun 12 19:21:40 Vili dbus[650]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Jun 12 19:21:40 Vili dbus[650]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Jun 12 19:23:53 Vili dbus[650]: [system] Reloaded configuration
Jun 12 19:23:53 Vili dbus[650]: [system] Reloaded configuration
Jun 12 19:23:53 Vili dbus[650]: [system] Reloaded configuration
Jun 12 19:23:53 Vili dbus[650]: [system] Reloaded configuration
Jun 12 19:24:14 Vili dbus[650]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jun 12 19:24:14 Vili dbus[650]: [system] Successfully activated service 'org.freedesktop.hostname1'
> ps axf | grep dbus
650 ? Ss 0:06 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
19102 pts/3 S+ 0:00 \_ /usr/bin/grep dbus
1914 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --sessionLooking at the dmesg logs I do see the following error that occurred when I logged in
Jun 12 19:20:37 Vili login[16320]: pam_unix(login:session): session opened for user vendion by LOGIN(uid=0)
Jun 12 19:20:37 Vili systemd[1]: Created slice User Slice of vendion.
Jun 12 19:20:37 Vili systemd[1]: Starting User Manager for UID 1000...
Jun 12 19:20:37 Vili systemd-logind[647]: New session c2 of user vendion.
Jun 12 19:20:37 Vili systemd[16327]: user@1000.service: Failed at step CGROUP spawning /usr/lib/systemd/systemd: No such file or directory
Jun 12 19:20:37 Vili systemd[1]: Started Session c2 of user vendion.
Jun 12 19:20:37 Vili systemd[1]: Started User Manager for UID 1000.
Jun 12 19:20:37 Vili login[16320]: LOGIN ON tty1 BY vendion
Jun 12 19:20:39 Vili dbus[650]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
Jun 12 19:20:40 Vili systemd[1]: Starting Location Lookup Service...
Jun 12 19:20:40 Vili dbus[650]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Jun 12 19:20:40 Vili systemd[1]: Started Location Lookup Service.I'm not sure what to make of the "No such file or directory" as /usr/lib/systemd/systemd is a file on my system and has both read and executable bits
> file /usr/lib/systemd/systemd
/usr/lib/systemd/systemd: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=8d3cb750275dc2f474dc7f049fdffb3a649b1d49, stripped
> ls -l /usr/lib/systemd/systemd
-rwxr-xr-x 1 root root 1104576 Jan 28 17:32 /usr/lib/systemd/systemd*I don't use a login manager, instead I just login via tty1 and then run startx to start up X11 and run my window manager, in case this matters. I'm kind of stumped on what else to check to try and fix this, I don't see anything posted on the "Latest News" section of the homepage about any breakage/manual changes required, at the same time I didn't make any configuration changes that I remember so I'm not 100% certain it was a package update that broke things.
Anyone here have any ideas?
Last edited by vendion (2017-06-13 00:23:32)
Offline
What's in your xinitrc?
Offline
So I think I figured it out, it seems gpg-agent.service causing problems as after deleting $HOME/.config/systemd/user/default.target.wants/gpg-agent.service and logged out and back in and everything seems to be working now and running systemctl --user status works as expected.
Not exactly sure how and why gpg-agent.service was breaking my user session but it seems to be the culprit.
Edit: I guess my fault for not checking the Wiki first as the section on starting gpg-agent via SystemD User has changed since I last checked it.
Last edited by vendion (2017-06-13 00:22:49)
Offline