Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1232568

Summary: Clarification of VNCServer Setup Documentation Requsted
Product: [Retired] Fedora Documentation Reporter: eckirchn
Component: system-administrator's-guideAssignee: Stephen Wadeley <swadeley>
Status: CLOSED DEFERRED QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: eckirchn, pbokoc, swadeley
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-31 13:36:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description eckirchn 2015-06-17 04:20:14 UTC 
using:

https://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_Guide/ch-TigerVNC.html#configuring-vncserver-2users

[in the below statements X = {1, 2, 3....10}]

I was able to install and connect to a VNC session using "vncviewer -via XXXXX" however it was only after executing "systemctl start vncserver@:X.service' on the remote machine.

Executing 
  systemctl enable vncserver@:X.service

results in:
  Failed to execute operation: No such file or directory



Section 8.1.3. Starting VNC Server states:
  systemctl enable vncserver@:display_number.service

however, unless one creates a file such as: 
  vncserver@:X.service

the command 
 systemctl enable vncserver@:X.service

does not work.  After some time with the help of [coolmadmax] on IRC://#Fedora, I was able to understand this was where I was missing a step.

I think it would help to add some clarifying statements here to help others.  

The guide [coolmadmax] suggested:  
  https://stufs4u.wordpress.com/2014/02/25/install-and-configure-vnc-server-in-fedora-20/
added this ounce of clarification.

Help on this issue included [mutk] [fenrus02] [kendell] [devhen] and [_AnK] and I thank all.
Comment 1 Stephen Wadeley 2015-06-17 22:11:20 UTC 
Hello

Thank you for raising this bug.

As stated in "Configuring the first VNC connection", specifying the display number in the configuration file is not required. I did test this a few months ago and raised a bug to get the man page fixed.

Bug 1195266 - The display number is not required in the file name for VNC

However I will test the enable command soon.
Comment 2 Stephen Wadeley 2016-11-21 21:12:23 UTC 
Hello

For Fedora 24, see also 

Bug 1383089 - Inconsistent steps for TigerVNC
Comment 3 Petr Bokoc 2024-05-31 13:36:40 UTC 
Migrated to https://gitlab.com/fedora/docs/fedora-linux-documentation/fedora-linux-sysadmin-guide/-/issues/14.