When running an application like firefox or virt-manager, the following dbus processeses are still active after the application has been closed:

# ps -ef|grep -i dbus
dbus      2321     1  0 Jun12 ?        00:00:32 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root     24727     1  0 17:56 ?        00:00:00 dbus-launch --autolaunch f5d16dc35d45457d9c19554b864e054d --binary-syntax --close-stderr
root     24728     1  0 17:56 ?        00:00:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session


After hitting ^C on the hanging logout the dbus process started by the application is killed:

# ps -ef|grep -i dbus
dbus      2321     1  0 Jun12 ?        00:00:32 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

After that the ssh session will close.

*** Bug 1208893 has been marked as a duplicate of this bug. ***

There is a patch on the D-Bus bugzilla which can probably be adapted to make the autostarted bus exit after there are no more client connections. It can probably be rebased without too much difficulty.

David, did oyu have a chance to look at adapting those patches ?

Realistically, this is a duplicate of bug 1460262 (which has a somewhat different description of the problem). I have added it as a blocker, so at least the bugs are visibly linked.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0765