Bug 1806992
Summary: | Rebase tigervnc to 1.10.1 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Grulich <jgrulich> |
Component: | tigervnc | Assignee: | Jan Grulich <jgrulich> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | Lucie Vařáková <lmanasko> |
Priority: | unspecified | ||
Version: | 8.2 | CC: | ayadav, bsanford, lmanasko, mkrajnak, tpelka, vkadlcik |
Target Milestone: | rc | Keywords: | Rebase |
Target Release: | 8.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tigervnc-1.10.1-1.el8 | Doc Type: | Enhancement |
Doc Text: |
.tigervnc has been rebased to version 1.10.1
The `tigervnc` suite has been rebased to version 1.10.1. The update contains number of fixes and improvements. Most notably:
* tigervnc now only supports starting of the virtual network computing (VNC) server using the `systemd` service manager.
* The clipboard now supports full Unicode in the native viewer, `WinVNC` and Xvnc/libvnc.so.
* The native client will now respect the system trust store when verifying server certificates.
* The Java web server has been removed.
* `x0vncserver` can now be configured to only allow local connections.
* `x0vncserver` has received fixes for when only part of the display is shared.
* Polling is now default in `WinVNC`.
* Compatibility with VMware's VNC server has been improved.
* Compatibility with some input methods on macOS has been improved.
* Automatic "repair" of JPEG artefacts has been improved.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 03:00:07 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: | |||
Bug Depends On: | 1818716 | ||
Bug Blocks: |
Description
Jan Grulich
2020-02-25 12:20:35 UTC
There is no completely different way how to start tigervnc server. Here are the steps you have to follow in order to run a vnc server: 1) You need to load SELinux policy, you can do that with following commands: $ sudo semodule -i /usr/share/selinux/packages/vncsession.pp $ sudo restorecon /usr/sbin/vncsession /usr/libexec/vncsession-start 2) You don't need to do any changes to the vncserver service file, it will be used as it is. You just need to modify /etc/tigervnc/vncserver.users, where you can configure which display number will be used for which user. For example if you use: :2=jgrulich then starting vncserver@:2 will start for user named "jgrulich". If you open that file you will see examples there so it should be pretty straightforward. 3) To configure Xvnc parameters, you can modify /etc/tigervnc/vncserver- config-defaults. These will be used to override builtin default options and starting point for per-user configuration stored in ~/.vnc/config. You can then modify ~/,vnc/config for each user to use whatever option you want to use for a specific user. Using /etc/tigervnc/vncserver-config-mandatory you can override default configuration and also the configuration which is configured in user directories. This can be used probably by administrators forcing certain configuration. 4) Tigervnc now also uses desktop files located in /usr/share/xsessions to start particular desktop. If you want to use for example GNOME, then you have to put "session=gnome" into one of the configuration files mentioned above. The value should match desktop file name. 5) Now you can start a session using: $ sudo systemctl start vncserver@:2 6) Connect from vncviewer \o/. Additional notes: 1) You cannot start a service for a user who is currently logged in (graphically) 2) Make sure you remove old service files which previously had to be copied to /etc/systemd/system as these will be loaded first and it will obviously fail. The new service file is in /usr/lib/systemd/system. I just created this doc https://docs.engineering.redhat.com/display/DESKTOPQE/VNCServer+using+systemctl and with Jan's input, this should verify that it is rebased and works. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (tigervnc bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4683 |