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.
DescriptionJ.H.M. Dassen (Ray)
2011-01-06 13:50:05 UTC
Created attachment 472052[details]
Proposed patch
Description of problem:
The tsclient version in RHEL6 has no apparent means of passing the client
hostname to rdesktop. This is a regression with respect to the tsclient that
came with RHEL5.
This becomes a problem for users that have to specify a client hostname to
avoid the bogus "No valid license available" message that the terminal
server spits out after many connects - specifying a bogus client hostname is
the only way to make further connections to the server.
Version-Release number of selected component (if applicable):
tsclient-2.0.2-6.el6
How reproducible:
100%
Steps to Reproduce:
1. Run "tsclient" in RHEL5.
2. Run "tsclient" in RHEL6, add a new connection of type "Windows Terminal
Service Connection", look for an option to enter client hostname
information.
Actual results:
1. Observe that the "Client Hostname" can be set in it for rdesktop client.
2. No option to enter client hostname information.
Expected results:
Option to enter client hostname information and have it passed to rdesktop.
Additional info:
Proposed patch (against upstream subversion's branches/tsclient-unstable
attached. The glade file part of this patch is fairly large due to changes
having been made through the glade-2 rather than directly. It can probably
be trimmed down for upstream submission.
Comment 1J.H.M. Dassen (Ray)
2011-01-06 19:53:43 UTC
Created attachment 472122[details]
Proposed patch
Revised patch - trimmed down the changes to the glade file.
I've verified that with this patch there are no additional glade warnings or Gtk messages beyond those that are generated with a build from unmodified upstream svn branch tsclient-unstable.
Comment 2J.H.M. Dassen (Ray)
2011-04-14 07:34:17 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.
http://rhn.redhat.com/errata/RHBA-2011-1662.html
Created attachment 472052 [details] Proposed patch Description of problem: The tsclient version in RHEL6 has no apparent means of passing the client hostname to rdesktop. This is a regression with respect to the tsclient that came with RHEL5. This becomes a problem for users that have to specify a client hostname to avoid the bogus "No valid license available" message that the terminal server spits out after many connects - specifying a bogus client hostname is the only way to make further connections to the server. Version-Release number of selected component (if applicable): tsclient-2.0.2-6.el6 How reproducible: 100% Steps to Reproduce: 1. Run "tsclient" in RHEL5. 2. Run "tsclient" in RHEL6, add a new connection of type "Windows Terminal Service Connection", look for an option to enter client hostname information. Actual results: 1. Observe that the "Client Hostname" can be set in it for rdesktop client. 2. No option to enter client hostname information. Expected results: Option to enter client hostname information and have it passed to rdesktop. Additional info: Proposed patch (against upstream subversion's branches/tsclient-unstable attached. The glade file part of this patch is fairly large due to changes having been made through the glade-2 rather than directly. It can probably be trimmed down for upstream submission.