RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1883432 - Tigervnc cannot use boolean values in config files [rhel-8.3.0.z]
Summary: Tigervnc cannot use boolean values in config files [rhel-8.3.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tigervnc
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1883415
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-29 08:33 UTC by RHEL Program Management Team
Modified: 2020-12-15 17:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1883415
Environment:
Last Closed: 2020-12-15 17:01:43 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 6 Martin Krajnak 2020-10-14 09:26:05 UTC 
tigervnc-server-1.10.1-9.el8_3.x86_64
tigervnc-server-minimal-1.10.1-9.el8_3.x86_64
tigervnc-selinux-1.10.1-9.el8_3.noarch
tigervnc-1.10.1-9.el8_3.x86_64
tigervnc-icons-1.10.1-9.el8_3.noarch
tigervnc-license-1.10.1-9.el8_3.noarch
tigervnc-server-module-1.10.1-9.el8_3.x86_64


After consultation with Jan, I tested with 2 reproducers:

1.Make sure that vnc session is working properly
2.Edit config in user directory, disable ipv4 with boolean value
# cat /home/vncuser/.vnc/config
UseIPv4=0
3.Restart vncservice
# systemctl restart vncserver@\:55.service 

4.Verify that vncservice is running:
# systemctl status vncserver@\:55.service 
● vncserver@:55.service - Remote desktop service (VNC)
   Loaded: loaded (/usr/lib/systemd/system/vncserver@.service; disabled; vendor preset: disabled)
   Active: active (running) since Wed 2020-10-14 11:14:54 CEST; 1s ago
  Process: 14203 ExecStart=/usr/libexec/vncsession-start :55 (code=exited, status=0/SUCCESS)
 Main PID: 14210 (vncsession)
    Tasks: 1 (limit: 25029)
   Memory: 2.1M
   CGroup: /system.slice/system-vncserver.slice/vncserver@:55.service
           ‣ 14210 /usr/sbin/vncsession vncuser :55

5.Result: Cannot initiate connection to session on display:55.

=======================================

1.Make sure that vnc session is working properly
2.Edit global config, disable ipv4 with boolean value
# cat /etc/tigervnc/vncserver-config-defaults
....
UseIPv4=0
3.Restart vncservice
# systemctl restart vncserver@\:55.service 

4.Verify that vncservice is running:
# systemctl status vncserver@\:55.service 
● vncserver@:55.service - Remote desktop service (VNC)
   Loaded: loaded (/usr/lib/systemd/system/vncserver@.service; disabled; vendor preset: disabled)
   Active: active (running) since Wed 2020-10-14 11:14:54 CEST; 1s ago
  Process: 14203 ExecStart=/usr/libexec/vncsession-start :55 (code=exited, status=0/SUCCESS)
 Main PID: 14210 (vncsession)
    Tasks: 1 (limit: 25029)
   Memory: 2.1M
   CGroup: /system.slice/system-vncserver.slice/vncserver@:55.service
           ‣ 14210 /usr/sbin/vncsession vncuser :55


5. Result: Cannot initiate connection to session on display:55.
Comment 10 errata-xmlrpc 2020-12-15 17:01:43 UTC 
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:5484
Note You need to log in before you can comment on or make changes to this bug.