Re: checkX problems

[Ken Brown <kbrown at cornell dot edu>]

On 11/20/2009 2:47 PM, Gertjan van Noord wrote:
> On Fri, Nov 20, 2009 at 02:43:11PM -0500, Ken Brown wrote:
> > On 11/20/2009 12:14 PM, Charles Wilson wrote:
> > > I've integrated Lothar's patch into run2/checkX (along with some other
> > > internal changes), and published a test release.  Please try run-0.3.1-1
> > > and let me know if it fixes your problems with checkX.
> > I still have the instability that I reported as problem #2 in
> >
> >   http://cygwin.com/ml/cygwin-xfree/2009-10/msg00143.html
> >
> > but I wasn't expecting you to fix that.  As I said later in the
> > thread, I suspect BLODA.
> >
> > But the new behavior of the timeout option (my problem #1) works
> > fine, with one caveat:  If I start the X server with startxwin.bat,
> > it immediately exits and claims that a server is already running.
> > This was also reported earlier today by Jim Reisert:
> >
> >   http://cygwin.com/ml/cygwin-xfree/2009-11/msg00158.html
> >
> > Could it be that checkX is tricking XWin into thinking that a
> > different X server is running?  (I have no idea how XWin decides
> > whether an X server is running, so this may or may not be
> > plausible.)  Strangely, the problem doesn't occur if I use
> > startxwin.sh instead of startxwin.bat.
>
>
> has it something to do with the -wait option to checkX that is present
> in the startxwin.bat? I had to remove that option, since it broke 
> the start of the X server. And I now note it is not in the bash version.

If you remove -wait but still start checkX with run, then you might as 
well not use checkX at all.  (run will return immediately, leaving 
checkX running in the background.)

Ken

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