Bug 1383089

Summary: Inconsistent steps for TigerVNC
Product: [Fedora] Fedora Documentation Reporter: Lukas Zapletal <lzap>
Component: system-administrator's-guideAssignee: Stephen Wadeley <swadeley>
Status: ASSIGNED --- QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: jgrulich, swadeley
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1397207 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lukas Zapletal 2016-10-09 19:47:01 UTC 
Hi guys!

It looks like

https://docs.fedoraproject.org/en-US/Fedora/24/html/System_Administrators_Guide/ch-TigerVNC.html

is a bit out of date. The service changed the way it starts, it now requires two changes:

User=MY_USER
PIDFile=/home/MY_USER/.vnc/%H%i.pid

I also suggest to add Troubleshooting section:

A) When VNC server does not start, check status of the service (systemctl status), system journal or SELinux denials.

(I recently filed a bug 1383088 for Fedora 24 on that topic)

B) TigerVNC enforces encryption when using password authentication. Some clients (outdated or MacOS built-in Shared Screen application) won't be able to connect.
Comment 1 Stephen Wadeley 2016-10-10 21:23:55 UTC 
Thank you for raising this bug.

 I will test and update accordingly.
Comment 2 Stephen Wadeley 2016-11-21 22:04:50 UTC 
(In reply to Lukas Zapletal from comment #0)
> Hi guys!
> 
> It looks like
> 
> https://docs.fedoraproject.org/en-US/Fedora/24/html/
> System_Administrators_Guide/ch-TigerVNC.html
> 
> is a bit out of date. The service changed the way it starts, it now requires
> two changes:
> 
> User=MY_USER
> PIDFile=/home/MY_USER/.vnc/%H%i.pid
> 
and the instructions in the file [1] do not tell you to replace <user> with a valid user. I can clone this bug for that.

[1] /lib/systemd/system/vncserver@.service