Bug 1897498

Summary:	Starting the xvnc service starts a vncsession process and goes into zombie state
Product:	Red Hat Enterprise Linux 8	Reporter:	amit yadav <ayadav>
Component:	tigervnc	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED ERRATA	QA Contact:	Martin Krajnak <mkrajnak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.3	CC:	mkrajnak, pbhosale, tpelka, yuokada
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	tigervnc-1.11.0-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 15:28:37 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:

Description amit yadav 2020-11-13 08:33:26 UTC

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.

Comment 2 Jan Grulich 2020-11-16 11:16:55 UTC

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

Comment 7 Martin Krajnak 2020-11-25 14:19:40 UTC

tigervnc-server-1.11.0-2.el8.x86_64

Comment 9 errata-xmlrpc 2021-05-18 15:28:37 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 (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