This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: x apps cant start from bashW
- From: Rupert Brooks <rbrook at cim dot mcgill dot ca>
- To: Rupert Brooks <rbrook at McRCIM dot McGill dot EDU>
- Cc: cygwin-xfree at cygwin dot com
- Date: Sun, 6 Oct 2002 08:51:49 -0400 (EDT)
- Subject: Re: x apps cant start from bashW
- Reply-to: cygwin-xfree at cygwin dot com
Well that was premature - I just changed the nature of my problem. the
export issue fixed the local problem
However, upon ssh -Xg to a remote host (RedHat Linux, uses an XDM login,
so XDM is probably running when i login) I get the following messages
during the startup script of that host. I have tried on different
machines on this network, so the problem is not specific to one machine.
/usr/X11R6/bin/xauth: creating new authority file
/home/rain/rbrook/.Xauthority
/usr/X11R6/bin/xauth: unable to open tmp file
"/home/rain/rbrook/.Xauthority-n"
/usr/X11R6/bin/xauth: unable to write authority file
/home/rain/rbrook/.Xauthority-n
Then when I try an x client
rbrook@skinner{rbrook}xterm &
[1] 5721
rbrook@skinner{rbrook}X11 connection rejected because of wrong
authentication.
X connection to localhost:10.0 broken (explicit kill or server
shutdown).
So what I think is happening, is that
- ssh needs to set a fake authority cookie for the virtual display it
creats
- xauth cant set that cookie
- therefore Xapps cant send stuff out the channel.
Trouble is, I have absolutely no idea why xauth can't set that cookie. i
have successfully ssh -X'ed into this machine before and it all just
worked, first time.
So, if someone could give me a tip or two on how to diagnose what xauth is
whinging about - much appreciated.
Thanks
Rupert B.
On Sat,
5 Oct 2002, Rupert Brooks wrote:
> Solved my own problem; sorry to bother y'all
>
> FTR, the solution is that
> a) if the DISPLAY variable in bash is set without export, then when SSH
> starts up its not noticed, and then SSH does not notice where to send
> the X11 stream
>
> b) you have to set and export the display variable, it is neither set
> automatically, nor does ssh have a default.
>
> I'm a tcsh user, so didnt realize that necessity under bash.
>
> This seems to be covered in the SSH notes message, sorry I didn't see that
> before.
>
> Rupert B
>
>
> On Sat, 5 Oct 2002, Rupert Brooks wrote:
>
> > Hi
> > - having a strange problem here. Just installed a fresh install of
> > Cygwin / Xfree. startxwin.bat works, and an xterm appears. From that
> > xterm I can start other xapps and they work.
> >
> > BUT, from another cygwin bash shell, started independently, I get the
> > following error
> > xterm XT error: Can't open display:
> >
> > I have tried with numerous variations in the DISPLAY variable
> > localhost:0
> > localhost:0.0
> > 127.0.0.1:0
> > 127.0.0.1:0.0
> > 192.168.1.150:0.0
> >
> > etc
> >
> > I have done a tracert on all those addresses, and my routing seems ok,
> > that is packets for the localhost don't get routed out into the network
> > where the router might frig with them.
> >
> > Xwin.log shows no signs of having refused the connections. So I am
> > guessing that the request never made it to the Xserver.
> >
> > The problem I am ultimately trying to solve, is to get a remote connection
> > tunnelled over openSSH or putty. I have that setup on another machine,
> > and working well. there are two differences with this machine - this OS
> > is WinME not Win2K, and this one lives behind a LinkSys router.
> >
> > Anyway, I think I should get the local set up working right first before
> > trying to diagnose the SSH part. I don't see, though, why the router
> > should stop packets from the localhost. There is no firewall software on
> > this machine.
> >
> > Has anyone seen this before? Can anyone suggest where else to look?
> >
> > Thanks much
> > Rupert B.
> >
> >
>
>
--
--------------------------------------------------------------
Rupert Brooks
McGill Centre for Intelligent Machines (www.cim.mcgill.ca)
PhD. Student
http://www.cyberus.ca/~rbrooks
rbrook@cim.mcgill.ca
ICQ: 27978014 CELL: 6137997873
SMS: send short mail to <CELL#>@pcs.rogers.com