Not your normal DISPLAY problem.

[Suhaib Siddiqi]

I suspect it is problem on your local machine.  A while ago one of the user
had similar problem and he was able to fix it by reinstalling Windows :-O
Search mail archive, please.

Suhaib


> -----Original Message-----
> From: Larry Sanderson [ mailto:larrys@mrstock.com ] 
> Sent: Wednesday, May 30, 2001 9:19 PM
> To: Suhaib Siddiqi; cygwin-xfree@sourceware.cygnus.com
> Subject: Re: Not your normal DISPLAY problem.
> 
> 
> See comments inline...
> 
> > Are there any VPN, or Firewall software of "second fully
> functionalmachine"?
> Nope.  Both are on the same subnet, with no special
> 
> > When you start X-server do you get X-desktop?
> Yup.  The desktop comes up nicely.  In fact, X sessions from 
> the remote
> machine are working correctly... Just X sessions from 
> localhost are failing
> 
> > Can you run the following simple test from a bash shell?
> >
> > From Cygwin bash shell cd to /usr/X11R6/bin
> >
> > DISPLAY=127.0.0.1:0.0
> > Export DISPLAY
> No problems here... an 'echo $DISPLAY' verifies the value 
> 127.0.0.1:0.0
> 
> > ./Xwin :0&
> The X-desktop apears here, as expected.
> 
> > ./xterm&
> > ./twm&
> Both these return the same "Can't open display".
> 
> > You should see an X-desktop, then an xterm.  If Xwin does 
> not start please
> > post exact error messages to the list.
> >
> > Suhaib
> 
> Thanks for your help, but I've spent a couple days on this, 
> and I can't seem
> to find the problem.  It's as if the X-programs are failing 
> to communicate
> over the network.  Could it be somewhere in the network 
> settings?  At this
> point I'm pretty sure it isn't actually a problem with the 
> DISPLAY variable.
> 
> Thanks for any further help you can offer.
> 
> -Larry
> 
> >
> > > At first glance, the "Can't open display" error I'm 
> getting seems the
> > > run-of-the-mill variety... Just make sure the X-server is 
> running, and
> the
> > > DISPLAY variable is properly set.  But...
> > >
> > > If I'm on a second (fully functional) box, and set the 
> DISPLAY to point
> to
> > > the problem machine, the X-programs pop up just fine. So, 
> the X-server
> > > seems
> > > to be running correctly.  If I'm on the first and point 
> the DISPLAY to
> > > itself (or to the second fully functional one) then 
> nothing works... I
> > > always get the "Can't open display" error.
> > >
> > > It seems as though either the DISPLAY variable isn't being read
> correctly,
> > > or I'm doing something incredibly stupid.
> > >
> > > Any insight?
> > >
> > > -Larry
> 
>