TigerVNC arbitrarily starts on unspecified ports

Solution Verified - Updated -

Issue

  • When attempting to start VNC on a specific port, the VNC server will pick an alternate port if the specified port is in use. This will result in running VNC on unexpected ports - and possibly running unexpected VNC servers. This behavior deviates significantly from upstream.

Environment

  • Red Hat Enterprise Linux 7
  • tigervnc-server package version earlier than 1.8.0-21

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content