Mail Archives: cygwin/2003/01/27/13:10:34
ejfried AT ca DOT sandia DOT gov wrote:
----------------->>>>
Not that this is sure to solve your problem, but it's a possibility:
ssh daemons can be configured to prohibit X forwarding. Try
ssh -v -l <user> <system> <x app>
to see what ssh reports regarding whether X forwarding was actually
established, and/or check the sshd_config file on the remote machine
(if you have permission; otherwise, ask the admin.)
----------------->>>>
My other Linux systems can connect to the remote sshd. Here is the output
of a call:
-------snip----------
debug1: Sending command: evolution
debug1: channel request 0: exec
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug1: channel 0: rcvd eof
debug1: channel 0: output open -> drain
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: rcvd close
debug1: channel 0: close_read
debug1: channel 0: input open -> closed
Gtk-WARNING **: cannot open display:
debug1: channel 0: obuf empty
debug1: channel 0: close_write
debug1: channel 0: output drain -> closed
debug1: channel 0: almost dead
debug1: channel 0: gc: notify user
debug1: channel 0: gc: user detached
debug1: channel 0: send close
debug1: channel 0: is dead
debug1: channel 0: garbage collecting
debug1: channel_free: channel 0: client-session, nchannels 1
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 4.7 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 1
-------snip----------
Any ideas would be great. Should this work?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -