Description of problem: On fresh and update-to-date installation of Fedora 32 x86_64, dnf install tigervnc-server reports "complete!" but does not not install /usr/bin/vncserver. During installation, the message: "Failed to preset unit: Unit file xvnc.service does not exist" appears in the console output. Version-Release number of selected component (if applicable): 1.11.0-1.fc32 How reproducible: Try to install tigervnc-server on a fresh F32 installation. Steps to Reproduce: 1. Install Fedora 32 x86_64 Workstation 2. sudo dnf update 3. sudo dnf install tigervnc-server Actual results: which vncserver reports no such executable Expected results: tigervnc-server should install all vncserver components Additional info: Apparently systemd service renaming is the source of this sort of problem.
The error message "Failed to preset unit: Unit file xvnc.service does not exist" is an issue in the spec file, I will fix that. The missing vncserver is expected as Tigervnc is supposed to be started over systemd now. There is a newer build of Tigervnc providing /usr/bin/vncserver, but it's just a script that will tell you to read HOWTO.md document.
FEDORA-2020-7f2dcfe858 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-7f2dcfe858
FEDORA-2020-98137c59f8 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-98137c59f8
Systemd start implies tigernvc-server users require root privilege, correct? If so, that's a step backward in usability.
Thanks for the speedy update to the install problem.
FEDORA-2020-7f2dcfe858 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-7f2dcfe858` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7f2dcfe858 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-98137c59f8 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-98137c59f8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-98137c59f8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Applied patch as directed on F32. Executing /usr/bin/vncserver gives: Please read /usr/share/doc/tigervnc/HOWTO.md for more information. However, /usr/share/doc/tigervnc/HOWTO.md was not installed.
Other than missing HOWTO, install script errors are now gone.
Fedora documentation here still refers to /usr/bin/vncserver. https://docs.fedoraproject.org/en-US/Fedora/24/html/System_Administrators_Guide/ch-TigerVNC.html
(In reply to Steve King from comment #8) > Applied patch as directed on F32. Executing /usr/bin/vncserver gives: > > Please read /usr/share/doc/tigervnc/HOWTO.md for more information. > > However, /usr/share/doc/tigervnc/HOWTO.md was not installed. Thanks for spotting this, it should be fixed with the next build.
Looking good now! Confirmed install looks clean and howto exists. New /usr/share/doc/tigervnc/howto.md was clear and provided useful warnings for common pitfalls. Following directions in the howto, the vncserver started fine. A few minor requests for the HOWTO: 1) How do users know if they have a vncserver already running? Previously was vncserer -list. 2) How do users kill their VNC session? Previously was vncserver -kill :n 3) Confirm users should copy /etc/tigervnc/vncserver-config-defaults to their ~/.vnc/config and modify to suit. Thanks for the help!
Everything goes through systemd so: > A few minor requests for the HOWTO: > 1) How do users know if they have a vncserver already running? Previously > was vncserer -list. systemctl status vncserver@:x > 2) How do users kill their VNC session? Previously was vncserver -kill :n systemctl stop vncserver@:x > 3) Confirm users should copy /etc/tigervnc/vncserver-config-defaults to > their ~/.vnc/config and modify to suit. Well, this step is not necessary unless they want specific configuration. I will update the HOWTO with the information above. Thank you.
FEDORA-2020-7f2dcfe858 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-98137c59f8 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.