Description of problem:
If Xvnc is launched with timers, it does not remove /tmp/.X<display>-lock file nor the unix domain socket in /tmp/.X11-unix/X<display>.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the latest tigervnc server on RHEL7 (currently tigervnc-server-minimal-1.8.0-17.el7.x86_64)
2. Choose an unused X display number (15 for instance)
3. Make sure there is neither a /tmp/.X15-lock lock file nor /tmp/.X11-unix/X15 unix domain socket.
4. Launch the Xvnc with timers (60 seconds for maximum disconnection time, 90 seconds for maximum idle time):
$ Xvnc :15 -bs -nolisten tcp -verbose -localhost -MaxDisconnectionTime=60 -MaxIdleTime=90
5. Wait 60 second so that the Idle timer will be executed
6. Check whether /tmp/.X15-lock and /tmp/.X11-unix/X15 are still there.
There are leftover lock and unix domain socket files:
# ls -l /tmp/.X15-lock /tmp/.X11-unix/X15
srwxrwxrwx. 1 root root 0 Aug 15 09:17 /tmp/.X11-unix/X15
-r--r--r--. 1 root root 11 Aug 15 09:17 /tmp/.X15-lock
No /tmp/.X11-unix/X15 and /tmp/.X15-lock files.
It seems this has been fixed upstream in : https://github.com/TigerVNC/tigervnc/issues/727
I am able to reproduce the issue with tigervnc-server-minimal-1.9.0-3.fc29.x86_64 as well.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.