public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin-xfree@cygwin.com
Subject: Re: X server fails to start
Date: Tue, 29 Dec 2009 07:01:00 -0000	[thread overview]
Message-ID: <4B39A925.1050309@cwilson.fastmail.fm> (raw)
In-Reply-To: <loom.20091228T222649-537@post.gmane.org>

Feng Dai wrote:

> The root cause is checkX doesn't work properly. It cause XWin failed on
> initClipboard and exit itself. The work around is either comment out checkX or
> have a "sleep 3" to let XWin server startup before checkX runs.

It's actually not checkX's fault that the Xserver dies.  All checkX does
is try to call XOpenDisplay(). However, in the current usage by the
startup scripts, checkX will do so /repeatedly/ during the period when
the Xserver is just getting started.

XWin appears to be fragile at that stage in its execution.

So, the latest version of checkX tries to be gentle with the Xserver
when that Xserver is just launching.

To try it out, you should make the relevant part of startxwin.bat look
like this:

...
%RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error"

REM Make sure XWin is ready to accept connections before proceeding
checkX -d %DISPLAY% -t 12
...

That is, don't use %RUN% to invoke checkX.

--
Chuck

--
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/


  reply	other threads:[~2009-12-29  7:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 13:48 Csaba Raduly
2009-12-26 17:00 ` Michael Lutz
2009-12-28 21:40   ` Feng Dai
2009-12-29  7:01     ` Charles Wilson [this message]
2009-12-29  7:02       ` Charles Wilson
2009-12-29 17:03         ` Feng Dai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B39A925.1050309@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).