Bug 1994964

Summary:	SecureCRT SSH client is hard to type characters in an SSH session to Red Hat Enterprise Linux 8.4 with GUI installed
Product:	Red Hat Enterprise Linux 8	Reporter:	Flos Qi Guo <qguo>
Component:	openssh	Assignee:	Dmitry Belyavskiy <dbelyavs>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	jjelen
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-19 12:50:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Flos Qi Guo 2021-08-18 08:40:12 UTC

> Description of problem:
After upgrading the SSH server to Red Hat Enterprise Linux 8.4, no response or a big delay while typing the keyboard after connect to the sever with SecureCRT SSH client.

> Version-Release number of selected component (if applicable):
openssh-server-8.0p1-5.el8.x86_64
dbus-x11-1.12.8-12.el8.x86_64

> How reproducible:
Always

> Steps to Reproduce:
1. Fresh install an RHEL8.4 server with GUI
2. Connect to the RHEL8.4 server with SecureCRT ssh client which has 'Forward X11 packets' option enabled
3.

> Actual results:
After the session is built, typing on the SecureCRT ssh client is slow and can have no response or long delay.

> Expected results:
No delay when typing. 

> Additional info:
This issue can be solved by moving the ssh-x-forwarding* profiles to other place:

# mv /etc/profile.d/ssh-x-forwarding* /root

or disabling the 'Forward X11 packets' option from SecureCRT.

This issue seems like a regression of rhbz#1874282.

Comment 1 Jakub Jelen 2021-08-18 12:23:29 UTC

Should we move this to dbus, as the file /etc/profile.d/ssh-x-forwarding is provided by dbus and not by openssh? Isn't it a duplicate of bug #1940067 ?

Comment 2 Flos Qi Guo 2021-08-19 10:34:29 UTC

Yes, Paul's comment indicates we should hit the same issue. We can mark this bug duplicated. Thanks Jakub!

Comment 3 Jakub Jelen 2021-08-19 12:50:58 UTC


*** This bug has been marked as a duplicate of bug 1940067 ***