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.

Description of problem:

Whenever I start the Xvnc service for any user, a process of vncsession also starts and goes into zombie state. If I stop the user's vnc service, the zombie process is also cleaned up.

Version-Release number of selected component (if applicable):
tigervnc-server-1.10.1-7.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure vnc service as per https://access.redhat.com/solutions/5544351
2. Start the vncserver service

Actual results:
vncsession process is going into Zombie state.

root       26082  0.0  0.0      0     0 ?        Z    09:38   0:00 [vncsession] <defunct>    


Expected results:
Additional vncsession process should not start and go into Zombie state.

Additional info:

This is not affecting the vncsession service. But it is causing confusion.

Opened a bug in upstream with a potential fix: https://github.com/TigerVNC/tigervnc/issues/1148

tigervnc-server-1.11.0-2.el8.x86_64

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 (Moderate: tigervnc security, 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/RHSA-2021:1783