FS#63189 - systemd user actions not seen for user dbus
Attached to Project:
Community Packages
Opened by Jonas DOREL (jdorel) - Sunday, 14 July 2019, 10:27 GMT
Last edited by Balló György (City-busz) - Monday, 02 September 2019, 08:10 GMT
Opened by Jonas DOREL (jdorel) - Sunday, 14 July 2019, 10:27 GMT
Last edited by Balló György (City-busz) - Monday, 02 September 2019, 08:10 GMT
|
Details
Description:
When monitoring the user dbus with `busctl --user monitor` in terminal A, and activating a user unit with `systemctl --user start <unit>` in terminal B, I cannot see anything in terminal A. journalctl -eu indicates to me that that `busctl --user monitor` connects correctly: ``` Jul 14 11:46:37 notebook dbus-daemon[1013]: [session uid=1000 pid=1013] Connection :1.7007 (uid=1000 pid=11514 comm="busctl --user monitor ") became a monitor. ``` The dbus daemons are running: (result from ps -aux | grep dbus) ``` dbus 487 0.0 0.0 11532 1808 ? Ss Jul11 3:17 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only jdorel 1013 0.0 0.0 10908 1424 ? Ss Jul11 0:09 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only jdorel 1118 0.0 0.0 10512 908 ? S Jul11 0:02 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 ``` Systemd is registered: (busctl --user | grep systemd) ``` busctl --user | grep systemd :1.0 847 systemd jdorel :1.0 user@1000.service - - org.freedesktop.DBus 847 systemd jdorel - user@1000.service - - org.freedesktop.systemd1 847 systemd jdorel :1.0 user@1000.service - - ``` Environment: Xorg + i3 started through zshrc Context: I am trying to monitor my user services, so that I can get notified when a service fails. I could use OnFailure= in my units, but I want to monitor my user services globally. To do that, I want to monitor DBus for system change (Member=UnitRemoved). Additional info: systemd 242 (242.32-3-arch) |
This task depends upon
Closed by Balló György (City-busz)
Monday, 02 September 2019, 08:10 GMT
Reason for closing: Not a bug
Additional comments about closing: You can ask help in our forum.
Monday, 02 September 2019, 08:10 GMT
Reason for closing: Not a bug
Additional comments about closing: You can ask help in our forum.
```
$ for pid in 1118 1013; do echo $(</proc/$pid/environ tr \\0 \\n | grep -E '^DBUS_SESSION_BUS_ADDRESS='); done
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
```
strace will happily show you this:
$ strace -e connect systemctl --user >/dev/null
connect(3, {sa_family=AF_UNIX, sun_path="/run/user/1000/systemd/private"}, 33) = 0
$ strace -e connect systemctl >/dev/null
connect(3, {sa_family=AF_UNIX, sun_path="/run/dbus/system_bus_socket"}, 30) = 0
So, it's expected that starting a user unit as a user doesn't trigger any activity visible through busctl monitor.
Anyway, should I close the bug or is the `at-spi-dbus-bus.service` initiating a dbus-daemon a bug in itself ?