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.

Description of problem:

SSH X11 forwarding without launching X Window Server on the client side causes half of the key inputs to disappear. This problem is caused by dbus-launch consuming stdin.
Need to fix /etc/profile.d/ssh-x-forwarding.(c)sh which was added in #1874282.

How reproducible:

Steps to Reproduce:

1. Prepare SSH client environment without X Window Server.
This can be done on Linux without running X Window Server, or on Windows.
2. Log into to a system via SSH with the -Y option.

Actual results:
Half of the key inputs before entering Ctrl + C disappear.

Expected results:
The key inputs does not disappear.


Additional info:

This behavior is described in the man of dbus-launch. If you start dbus-launch with --exit-with-session, it will monitor terminal until HUP is input from stdin if it can't connect to X server. This is the reason for the statement "This option is not recommended". I suggest using --exit-with-x11 instead.

Sanity only. All tests from our test suit pass.

I think there is more to fix in /etc/profile.d/ssh-x-forwarding.(c)sh.

Running 'ssh -X user@hosta xterm' works as expected and the xterm window shows up. The problem is when you terminate the xterm with 'exit', the ssh call is not terminated and hangs. The reason is that dbus-launch on hosta keeps running and doesn't terminate.

The same also happens with rsync calls which makes them hang. More details can also be found in https://bugzilla.redhat.com/show_bug.cgi?id=1874282

This all works fine in dbus-1.12.8-11 but is broken in dbus-1.12.8-12.

I've just tried with the latest dbus-1.12.8-14 from CentOS 8 Stream and the bug still persists.

I'm wondering what 'All tests from our test suit pass' means when a simple 'ssh -X user@hosta xterm' doesn't work correctly.

Am I missing something?

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 (dbus bug fix and enhancement update), 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-2021:4365