James Ertle wrote:
Fatal server error:
Can't read lock file /tmp/.X0-lock
As a workaround, you should be able to add -nolock to the command line used
to start Xwin (in startxwin.bat, I'm guessing, in your case).
Since a few people seem to have this problem, I'd like to get a resolution.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Sadly, I have no theory about how this could be happening, except perhaps it
could be related to 'unusual' permissions on /tmp which could somehow let you
create but not rename a file (so the output of 'ls -al /tmp' might
Jon TURNEY wrote:
James Ertle wrote:
Fatal server error:
Can't read lock file /tmp/.X0-lock
As a workaround, you should be able to add -nolock to the command line used
to start Xwin (in startxwin.bat, I'm guessing, in your case).
Since a few people seem to have this problem, I'd like to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
Ok, my archaeological investigations in this area have revealed that this
locking code probably wasn't enabled in 6.8.99. I don't think it is actually
giving any benefit, since we also have a native named mutex is used in the
