Red Hat Bugzilla – Bug 891802
RFE: systemd unit for Xvnc (not vncserver)
Last modified: 2017-04-11 09:45:12 EDT
Description of problem:
tigervnc-server currently contains a systemd unit file for vncserver, but it doesn't really work when one wishes to use VNC with XDMCP. Instead, something like this is needed:
Description=VNC remote display %I
ExecStart=/usr/bin/Xvnc -SecurityTypes None -query 127.0.0.1 $XVNC_OPTIONS %i
It would be nice to have something like this added to the tigervnc-server-minimal package.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I found this issue too. According to syslog, server is started and after killed. As workaround, I have commented ExecStop line (only this one) and now it work.
[root@eee901 system]# cat vncserver@:2.service
Description=Remote desktop service (VNC)
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l sergeil -c "/usr/bin/vncserver %i"
# ExecStop=/sbin/runuser -l sergeil -c "/usr/bin/vncserver -kill %i"
It looks like ExecStop= is not recognized correct. In case, if issue is in systemd, all services with ExecStop= line are affected.
It looks like issue is fixed in tigervnc-server-1.3.0-3.fc19.i686
Sergei: the issue you were seeing is bug #983232. *This* bug is a feature request for a different type of systemd file altogether.
There also should be a socket unit file. (xinetd is a thing of the past)
I've combined this solution :
and same story for centos that is not behind a firewall
with this one
ie use a systemd socket and service not xinetd
Then you have a working xdmcp and vnc setup.
Also a readme explaining how to use these two socket files with an adjustment of the /etc/gdm/custom.conf
# GDM configuration storage
Description=XVNC Per-Connection Daemon
ExecStart=-/usr/bin/Xvnc -inetd -query localhost -geometry 1024x768 -depth 24 -once -SecurityTypes=None -fp /usr/share/X11/fonts/misc
tigervnc-1.7.1-4.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2d0066d567
tigervnc-1.7.1-4.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2d0066d567
tigervnc-1.7.1-4.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.