Bug 158658 - tsclient rpm should require the vnc rpm
tsclient rpm should require the vnc rpm
Product: Fedora
Classification: Fedora
Component: tsclient (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
Depends On:
  Show dependency treegraph
Reported: 2005-05-24 12:26 EDT by Jens Knutson
Modified: 2013-03-05 22:43 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-02 01:13:40 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 Jens Knutson 2005-05-24 12:26:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Epiphany/1.6.1

Description of problem:
The tsclient RPM ought to require the vnc rpm, since tsclient offers VNC functionality, but if you don't have the VNC rpm installed, the VNC selector in the dropdown list in tsclient is just mysteriously greyed out, with no explanation of why.  Unless one is a Big Ol' Nerd(TM) like me, one would probably not know *why* it appears broken like this.

Basically, for the majority of people, tsclient will appear to be broken right out of the box for VNC.

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

How reproducible:

Steps to Reproduce:
1. Install tsclient.
2. Wonder why you can't use it for VNC
3. Depending on expertise, either do some dorking around with yum to discover that VNC isn't installed OR get pissed off and whine about Red Hat on a web forum.

Additional info:
Comment 1 Christian Iseli 2007-01-22 06:18:07 EST
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Comment 2 Jens Knutson 2007-01-22 10:36:14 EST
Confirmed - tsclient still doesn't require vnc

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