Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1373563 - Port offset of 5500 with Vncconnect
Summary: Port offset of 5500 with Vncconnect
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 25
Hardware: ppc64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F25PPCBeta
TreeView+ depends on / blocked
 
Reported: 2016-09-06 15:12 UTC by Éric Fintzel
Modified: 2017-12-12 10:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:17:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Éric Fintzel 2016-09-06 15:12:02 UTC 
Description of problem:

During the "QA:Testcase Anaconda User Interface VNC Vncconnect" test of the Fedora-Server-dvd-ppc64-25-Alpha-1.2.iso image on ppc64, under grub prompt:

- If no port is given to the vncconnect=CLIENT_IP_ADDR linux command, the VNC server use the default port 5500 to connect the client.

- If a port number is provided as vncconnect=CLIENT_IP_ADDR:PORT the VNC server connects to the port 5500+PORT of the client. The 5500 offset is required on the VNC client, using only PORT does not work. Not sure this is the expected behaviour.

Note since Fedora 20, the VNC default port is 5900, and we have to go back to Fedora 19 to have the 5500 port used by default.

Note the behaviour is the same for ppc64le too.
Comment 1 Fedora End Of Life 2017-11-16 19:02:12 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora  'version'
of '25'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.
Comment 2 Fedora End Of Life 2017-12-12 10:17:35 UTC 
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.