From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10226 invoked by alias); 12 Mar 2010 02:31:23 -0000 Received: (qmail 10216 invoked by uid 22791); 12 Mar 2010 02:31:22 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from web57306.mail.re1.yahoo.com (HELO web57306.mail.re1.yahoo.com) (66.196.100.42) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Fri, 12 Mar 2010 02:31:16 +0000 Received: (qmail 81130 invoked by uid 60001); 12 Mar 2010 02:31:14 -0000 Message-ID: <356433.80911.qm@web57306.mail.re1.yahoo.com> Received: from [70.18.189.17] by web57306.mail.re1.yahoo.com via HTTP; Thu, 11 Mar 2010 18:31:14 PST Date: Fri, 12 Mar 2010 02:31:00 -0000 From: Ken Klein Subject: Incorrect Cygwin/X behavior leads to .X0-lock related fatal error To: cygwin-xfree@cygwin.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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-03/txt/msg00040.txt.bz2 Here is tool behavior that seems like a bug in 1.7.1 related to the Cygwin/X FAQ item 3.4 (A2)called "Fatal server error: Can't read lock file /tmp/.X0-lock." I am posting this, because the faq item states that the buggy behavior happens "For reasons which are not well understood at present." This post presents what I consider to be incorrect behavior that leads to this error. If I log on as a user without admin rights (on Windows XP), and I start Cygwin/X using the XWin Server program shortcut, the referenced lock file gets created and gives me read/write access. The Everyone user just has read access. When I then close my XWin session, the lock file remains. I log out of Windows, then someone else logs on (also without admin rights), and they get the fatal error as described in the FAQ item, since they do not have write access to the lock file. If, however, I had originally started Cygwin/X by opening a Cygwin window then entering startx, when I eventually end my Cygwin session, the lock file gets deleted. So in this scenario, the next person to log on will not get the fatal error, since Cygwin didn't leave the lock file behind. My opinion is that the startx scenario behaves correctly, and the XWin Server shortcut scenario presents a bug, namely, it leaves behind the lock file after the session is ended. -- 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/