I can reproduce this. I added a "sleep 5" to a pm-utils sleep.5 script. When I run systemd-shim in the foreground in my session, I get this output after resuming:
14:39:18 O: GDBus-debug:Address: In g_dbus_address_get_for_bus_sync() for bus type 'session' 14:39:18 O: GDBus-debug:Address: env var DBUS_SESSION_BUS_ADDRESS is not set 14:39:18 O: GDBus-debug:Address: env var DBUS_SYSTEM_BUS_ADDRESS is not set 14:39:18 O: GDBus-debug:Address: env var DBUS_STARTER_BUS_TYPE is not set 14:39:18 O: GDBus-debug:Address: Running 'dbus-launch --autolaunch=daca3d32fc003f5e41857948525b8e7d --binary-syntax --close-stderr' to get bus address (possibly autolaunching) [...] 14:39:18 O: GDBus-debug:Address: dbus-launch stderr output: 14:39:18 O: 5994: Autolaunch enabled (using X11). 14:39:18 O: 5994: --exit-with-session automatically enabled 14:39:18 O: 5994: Connected to X11 display ':0.0' 14:39:18 O: 5994: dbus-daemon is already running. Returning existing parameters. 14:39:18 O: 5994: dbus-launch exiting 14:39:18 O: GDBus-debug:Address: Returning address 'unix:abstract=/tmp/dbus-MIO6Nrok3P,guid=7a808dc6cc702b9d36d2fc23528f5e40' for bus type 'session' 14:39:18 O: GDBus-debug:Auth: CLIENT: initiating 14:39:18 O: GDBus-debug:Auth: CLIENT: sent credentials 'GCredentials:linux-ucred:pid=5062,uid=0,gid=0' 14:39:18 O: GDBus-debug:Auth: CLIENT: writing 'AUTH\r\n' 14:39:18 O: GDBus-debug:Auth: CLIENT: WaitingForReject 14:39:18 O: GDBus-debug:Auth: CLIENT: WaitingForReject, read 'REJECTED EXTERNAL DBUS_COOKIE_SHA1 ANONYMOUS' 14:39:18 O: GDBus-debug:Auth: CLIENT: Trying to choose mechanism 14:39:18 O: GDBus-debug:Auth: CLIENT: Trying mechanism 'EXTERNAL' 14:39:18 O: GDBus-debug:Auth: CLIENT: writing 'AUTH EXTERNAL 30\r\n' 14:39:18 O: GDBus-debug:Auth: CLIENT: WaitingForOK 14:39:18 O: GDBus-debug:Auth: CLIENT: WaitingForOK, read 'OK 7a808dc6cc702b9d36d2fc23528f5e40' 14:39:18 O: GDBus-debug:Auth: CLIENT: writing 'NEGOTIATE_UNIX_FD\r\n' 14:39:18 O: GDBus-debug:Auth: CLIENT: WaitingForAgreeUnixFD 14:39:18 O: GDBus-debug:Auth: CLIENT: WaitingForAgreeUnixFD, read='AGREE_UNIX_FD' 14:39:18 O: GDBus-debug:Auth: CLIENT: writing 'BEGIN\r\n' 14:39:18 O: GDBus-debug:Auth: CLIENT: Done, authenticated=1 and indeed I see a new dbus daemon: root 4610 0.0 0.0 24444 624 pts/15 S 14:38 0:00 dbus-launch --autolaunch=daca3d32fc003f5e41857948525b8e7d --binary-syntax --close-stderr root 4613 0.0 0.0 30384 968 ? Ss 14:38 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session If I run the shim under env -u DISPLAY (as it would when being D-BUS activated), I get the same D-BUS errors as in the logs of the reporters. ** Changed in: systemd-shim (Ubuntu) Importance: Undecided => High ** Changed in: systemd-shim (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing resume signal because D-BUS connection goes away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs