From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16647 invoked by alias); 10 Nov 2010 16:25:53 -0000 Received: (qmail 16633 invoked by uid 22791); 10 Nov 2010 16:25:51 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from smtpout.karoo.kcom.com (HELO smtpout.karoo.kcom.com) (212.50.160.34) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 10 Nov 2010 16:25:47 +0000 Received: from 213-152-38-55.dsl.eclipse.net.uk (HELO [192.168.0.5]) ([213.152.38.55]) by smtpout.karoo.kcom.com with ESMTP; 10 Nov 2010 16:25:37 +0000 Message-ID: <4CDAC78F.1010402@dronecode.org.uk> Date: Wed, 10 Nov 2010 16:25:00 -0000 From: Jon TURNEY Reply-To: cygwin-xfree@cygwin.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: fergus@bonhard.uklinux.net Subject: Re: Updated: xorg-server-1.9.2-1 References: <4CD7E3A7.3060704@bonhard.uklinux.net> <4CD803CD.60603@dronecode.org.uk> <4CD90E42.5000308@bonhard.uklinux.net> In-Reply-To: <4CD90E42.5000308@bonhard.uklinux.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2010-11/txt/msg00022.txt.bz2 On 09/11/2010 09:02, Fergus wrote: >>> Fatal server error: >>> Can't read lock file /tmp/.X0-lock > >> Does /tmp/.X0-lock exists? Is it readable by you? > > Yes. Hmm. It's strange that the Xserver should choose to lie about that, then. The code in question really does just say... lfd = open(LockFile, O_RDONLY); if (lfd < 0) { unlink(tmp); FatalError("Can't read lock file %s\n", LockFile); } ... so I can't see much room for unpredictability. It would be helpful if you could strace XWin to see why it gets this wrong. Have you tried manually removing the lock file /tmp/.X0-lock? >> Are you sure /tmp is getting mounted successfully >> where you expect it to be? > > Yes. > >> Have you tried '-nolock', as suggested by [1] > > I hadn't then. > But I have now and as a consequence everything is working perfectly. > Thank you. > > (Over time I have occasionally had to moderate the syntax of both "XWin" and > "xterm" command lines to go from working to failing and back again to working. > This is just another example. On an earlier occasion, the recommended use of > -nolock failed. I am just happy when the current usage works. Thanks again.) Well, I can't deny this might be your experience, but that's not how things are supposed to work :-) -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/