Bug 1260806 - Instructions state incorrect/impossible port for VNC client connect
Instructions state incorrect/impossible port for VNC client connect
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-09-07 19:14 EDT by The PowerTool
Modified: 2015-09-08 10:21 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-09-08 10:21:02 EDT
Type: Bug
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 The PowerTool 2015-09-07 19:14:46 EDT
Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Launch installation
2. use kernel arg inst.text
3. select VNC (when offered)

Actual results:
On-screen text says connect using port 1

Expected results:
On-screen text should say connect using port 5901

Additional info:
I anticipate this error is the same across all Fedora 22 install options that lead to VNC but have not tested to verify this assumption.  I encountered this issue on i386 using https://download.fedoraproject.org/pub/fedora/linux/releases/22/Server/i386/iso/Fedora-Server-netinst-i386-22.iso
Comment 1 David Shea 2015-09-08 10:21:02 EDT
That's a display number, not a port number. VNC clients such as vncviewer interpert strings such as "hostname:1" as the first display on hostname, strings such as "hostname::5901" as port 5901 on hostname.

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