Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
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