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 1086971 - x11 channels keeping ssh connections open when running Qt programs
Summary: x11 channels keeping ssh connections open when running Qt programs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qt
Version: 6.5
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-12 04:19 UTC by Dave Johansen
Modified: 2017-12-06 12:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:09:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Hello World Qt application (208 bytes, text/x-c++src)
2014-04-12 04:19 UTC, Dave Johansen 		no flags Details
View All

Description Dave Johansen 2014-04-12 04:19:30 UTC 
Created attachment 885648 [details]
Hello World Qt application

Description of problem:
When running a Qt program over an ssh connection, not all of the x11 channels that are being created are closing. These remaining channels keep the ssh connection from closing when typing exit to end the session.

Version-Release number of selected component (if applicable):
4.6.2

How reproducible:
Always

Steps to Reproduce:
1. Copy the attached Hello World Qt application to a remote host
2. Build application on remote host (qmake-qt4 -project; qmake-qt4; make)
3. ssh to remote host with -v
4. Run qt_test and observe the number of x11 channels opened
5. Close qt_test and note that not all of the x11 channels were closed

Actual results:
x11 channels remain open after closing Qt application.

Expected results:
All x11 channels closed when application is closed.

Additional info:
I tried reproducing this with "ssh -X localhost" but it appeared to close all of the channels as expected.
Comment 3 Than Ngo 2014-11-20 16:48:32 UTC 
(In reply to Dave Johansen from comment #0)
> Created attachment 885648 [details]
> Hello World Qt application
> 
> Description of problem:
> When running a Qt program over an ssh connection, not all of the x11
> channels that are being created are closing. These remaining channels keep
> the ssh connection from closing when typing exit to end the session.
> 
> Version-Release number of selected component (if applicable):
> 4.6.2
> 
> How reproducible:
> Always
> 
> Steps to Reproduce:
> 1. Copy the attached Hello World Qt application to a remote host
> 2. Build application on remote host (qmake-qt4 -project; qmake-qt4; make)
> 3. ssh to remote host with -v
> 4. Run qt_test and observe the number of x11 channels opened
> 5. Close qt_test and note that not all of the x11 channels were closed
> 
> Actual results:
> x11 channels remain open after closing Qt application.
> 
> Expected results:
> All x11 channels closed when application is closed.
> 
> Additional info:
> I tried reproducing this with "ssh -X localhost" but it appeared to close
> all of the channels as expected.

i have tried your steps, 
./qt_test

debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from ::1 42952
debug1: channel 1: new [x11]
debug1: confirm x11
debug1: client_input_channel_open: ctype x11 rchan 6 win 65536 max 16384
debug1: client_request_x11: request from ::1 42953
debug1: channel 4: new [x11]
debug1: confirm x11
debug1: channel 4: FORCE input drain
debug1: channel 4: free: x11, nchannels 5
debug1: channel 1: FORCE input drain
debug1: channel 1: free: x11, nchannels 4

It just looks fine for me. Just info for you, it's expected that the it does not immediately close the channel, but instead sends a close request to the server and returns.
Comment 4 Dave Johansen 2014-12-03 18:05:39 UTC 
I can still reproduce this bug with RHEL 6.6 and other users on the CentOS mailing list have been able to as well ( http://lists.centos.org/pipermail/centos/2014-December/148286.html ), so can this issue be further investigated?
Comment 5 Jan Kurik 2017-12-06 12:09:43 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.