Bug 485976 - tsclient reports "Host is a required field" despite a host name being provided
tsclient reports "Host is a required field" despite a host name being provided
Product: Fedora
Classification: Fedora
Component: tsclient (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Søren Sandmann Pedersen
Fedora Extras Quality Assurance
Depends On:
Blocks: F11Target
  Show dependency treegraph
Reported: 2009-02-17 13:56 EST by Chris Williams
Modified: 2014-06-18 05:10 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-27 11:26:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Williams 2009-02-17 13:56:44 EST
Description of problem:
Using tsclient-2.0.2-1.fc11.i386 in rawhide, when trying to create a new connection for VNC, SSH or XDMCP, tsclient reports "Host is a required field" despite a host name being provided.

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

How reproducible:

Steps to Reproduce:
1. start tsclient
2. add a new connection
3. in Edit Connection dialog box, in General settings enter name of connection, in Details enter host. Despite a host being provided, be it short name, fqdn or IP, the "Host is a required field" message is displayed at the bottom of the Edit Connections window and OK remains grayed out.
Actual results:
"Host is a required field" message is displayed and OK remains grayed out.

Expected results:
OK should un-gray after host is entered and a new connection should be able to be created.

Additional info:
Comment 1 Jesse Keating 2009-03-17 17:57:51 EDT
Adding this to the target.  I don't think we'd slip the release, but we'd sure like to see it get fixed.
Comment 2 Matthias Clasen 2009-04-22 01:20:41 EDT
I've fixed this in tsclient-2.0.2-3.fc11
Comment 3 Bug Zapper 2009-06-09 07:28:18 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 4 Bug Zapper 2010-04-27 09:00:20 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Note You need to log in before you can comment on or make changes to this bug.