XWin does not erase lock file when exiting
Jon Turney
jon.turney@dronecode.org.uk
Tue Jan 4 16:17:21 GMT 2022
On 27/12/2021 23:25, Rodrigo Medina wrote:
> When XWin regularly exits, it removes the socket in /tmp/.X11-unix/ and closes
> the XWin.?.log file, but it does not erase the file
> /tmp/.X11-unix/X?.lock. This file is
> owned by the user and him alone can erase it. The same user can start
> XWin again, but another user cannot start XWin. Very annoying
> situation when different
> users work on the same machine. This problem was not present in the
> previous release I was using.
Thanks for reporting this issue.
This issue was introduced via a patch to xtrans in xserver 1.20.4-1.
I've updated the patch from upstream, and uploaded xserver 21.1.2-2,
which should fix this issue.
In this updated version, these lockfile are no longer used, so you can
simply remove any stale ones which exist.
More information about the Cygwin
mailing list