Fwd: Xwindows won't start (Can't read lock file)

Jon TURNEY jon.turney@dronecode.org.uk
Fri Nov 14 00:25:00 GMT 2008


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 get a resolution.

Yaakov,

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 DDX
code to prevent multiple servers with the same display number, before that
locking code is entered.

So, it might be expedient to disable this locking code for now, since it seems
to be generating problems. Attached is a quick patch to do that.

Note that SERVER_LOCK as a configuration has been removed in X.Org git master,
making the patch to turn it off larger, so we might well have to cross this
bridge again at a later date...
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygwin-server-lock-disable.patch
URL: <http://cygwin.com/pipermail/cygwin-xfree/attachments/20081114/1b6ea484/attachment.ksh>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


More information about the Cygwin-xfree mailing list