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.
Bug 1112339 - [SAP 7.5 BUG] Not all x11 channels are closed when exiting many X applications
Summary: [SAP 7.5 BUG] Not all x11 channels are closed when exiting many X applications
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dbus
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 7.1
Assignee: David King
QA Contact: Desktop QE
URL:
Whiteboard:
: 1208893 (view as bug list)
Depends On:
Blocks: 1002711 1289025 1393395 1420851 1460262 1479818 1496921 1522983 1531148
TreeView+ depends on / blocked
 
Reported: 2014-06-23 16:02 UTC by Frank Danapfel
Modified: 2023-03-24 13:29 UTC (History)
14 users (show)

Fixed In Version: dbus-1.10.24-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: sshX11freeze
Environment:
Last Closed: 2018-04-10 12:52:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 32509 0 None None None 2016-02-02 14:44:15 UTC
Red Hat Product Errata RHBA-2018:0765 0 None None None 2018-04-10 12:54:03 UTC

Comment 1 Frank Danapfel 2014-06-23 16:07:18 UTC 
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.
Comment 4 David King 2016-02-02 14:45:23 UTC 
*** Bug 1208893 has been marked as a duplicate of this bug. ***
Comment 5 David King 2016-02-09 16:33:01 UTC 
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.
Comment 6 Matthias Clasen 2016-05-13 16:43:23 UTC 
David, did oyu have a chance to look at adapting those patches ?
Comment 19 David King 2017-08-10 10:41:14 UTC 
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.
Comment 25 errata-xmlrpc 2018-04-10 12:52:20 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.