X forwarding works for Cygwin client but not for Debian
Hi I seem to be able to make X forwarding work between my Cygwin clients, but not between a Debian client and Cygwin SSH server(at least not properly). The weird thing is that I can run something like xcalc from the Debian shell without any issues, it just pops up as expected, but Gvim gives me error. This is what I get when I try to run Gvim from a connected Debian shell (ssh -X host) Vim: Caught deadly signal SYS Vim: Finished. Bad system call When I run vim I get no problem(in the forwarded connection), so I assume there is some kind of issue with the Gui version. I can connect to same server with a Cygwin client and run Gvim in a forwarded session no problem. I am really not sure what I am doing wrong here. I am not very literate about these problems. I do not even know what logs I can provide in this email. So if anyone needs to know more please let me know. I can try providing whatever is needed to figure out the issue. thanks -- 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/
X forwarding
I've been using XWinLogon to do X forwarding over SSH, to give a gnome-session on WinXP. That all worked fine, with a startup script of: SET PATH=c:\Program Files\xwinlogon SET DISPLAY=:0 start XWin_GL.exe :0 -clipboard -trayicon -bs -keyhook -nowinkill -nodecoration start xterm -e /usr/X11R6/bin/ssh -Y [EMAIL PROTECTED] gnome-session I uninstalled that and put Cygwin on, and haven't been able to get it to work. I've tried various ways of starting X, but I'll just begin with one way, to keep this post short! If I run startxwin.bat, I get a run.exe dialogue box: Error: could not start d:\cygwin\bin\xterm.exe'' -e /usr/bin/bash -l I took that line out of the script, so it just started X, and that works. The system tray icon says 0:0. In Cywin I then do ssh -Y [EMAIL PROTECTED] and get a command prompt from the Ubuntu server. Running a graphical app (eg gedit) returns cannot open display: (null) There are suggestions online to manually set the display, but as I understand that's incorrect if you are doing X forwarding. Any help would be appreciated! Steve -- View this message in context: http://www.nabble.com/X-forwarding-tf3282140.html#a9129611 Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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/
Re: X forwarding
SteveS wrote: [snip] In Cywin I then do ssh -Y [EMAIL PROTECTED] and get a command prompt from the Ubuntu server. Running a graphical app (eg gedit) returns cannot open display: (null) There are suggestions online to manually set the display, but as I understand that's incorrect if you are doing X forwarding. The suggestion meant to set DISPLAY on the client side (Cygwin), you are correct about not changing it on the server side. Just do: export DISPLAY=localhost:0:0 ssh -Y ... -- René Berber -- 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/
Re: X forwarding
Thanks for your help! René Berber-2 wrote: Just do: export DISPLAY=localhost:0:0 ssh -Y ... That's got me further, thanks! Gedit loads and gives a dialogue box: Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 (repeated about 30 times) Firefox works, but gives (at command line): GConf Error: Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 (twice) Steve -- View this message in context: http://www.nabble.com/X-forwarding-tf3282140.html#a9130229 Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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/
Problem with X forwarding by openssh-3.8p1
I have installed the lastest X11 binaries, including xorg-x11-xwin 6.7.0.0-3, together with openssh-3.8p1. The rest of my cygwin installation is also up-to-date, including cygwin1.dll version 1.5.9-1. I use startxwin.bat to start XWin using -multiwindow -clipboard. I login to a remote Linux server using ssh -X and start a Matlab session. The Matlab flash screen comes up, but when the flash screen disappears, there is only a menu bar located at the top left corner of the screen. If I choose maximize, the Matlab command window comes up but I am not able to type in any commands. If I downgrade to openssh-3.7.1p2-2, the problem disappears. The sshd_config file is identical in both cases. There are other problems with X forwarding under openssh-3.8p1, but since I am now using openssh-3.7.1p2-2, I cannot reproduce the error messages. I don't know whether this is considered an openssh-3.8p1 problem or a X server problem, but there appears to be some incompatibility issue here. Raymond Kwong This message was sent using IMP, the Internet Messaging Program.
Re: Problem with X forwarding by openssh-3.8p1
See A1: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-ssh-no-x11forwarding [EMAIL PROTECTED] wrote: I have installed the lastest X11 binaries, including xorg-x11-xwin 6.7.0.0-3, together with openssh-3.8p1. The rest of my cygwin installation is also up-to-date, including cygwin1.dll version 1.5.9-1. I use startxwin.bat to start XWin using -multiwindow -clipboard. I login to a remote Linux server using ssh -X and start a Matlab session. The Matlab flash screen comes up, but when the flash screen disappears, there is only a menu bar located at the top left corner of the screen. If I choose maximize, the Matlab command window comes up but I am not able to type in any commands. If I downgrade to openssh-3.7.1p2-2, the problem disappears. The sshd_config file is identical in both cases. There are other problems with X forwarding under openssh-3.8p1, but since I am now using openssh-3.7.1p2-2, I cannot reproduce the error messages. I don't know whether this is considered an openssh-3.8p1 problem or a X server problem, but there appears to be some incompatibility issue here. Raymond Kwong
invalid Window parameter error through ssh X forwarding
I have just upgraded my xfree-cygwin setup (Xwin serv Release 4.3.0-64, etc.). Some apps that worked through ssh without any problem with my previous setup (Xwin serv Release 4.3.0-58, etc.) are now exiting with errors messages related to an invalid Window parameter. For example, in a xterm after an ssh connect with X forwarding, gftp starts but as soon as I try to select a menu item, I get the following error: === [EMAIL PROTECTED] gourdeau]$ gftp [1] 13684 [EMAIL PROTECTED] gourdeau]$ Gdk-ERROR **: BadWindow (invalid Window parameter) serial 3647 error_code 3 request_code 38 minor_code 0 Gdk-ERROR **: BadAccess (attempt to access private resource denied) serial 3648 error_code 10 request_code 102 minor_code 0 [1]+ Exit 1 gftp === I have notice that the mouse cursor remains as an X and does not change to an arrow when moved over the gftp application. I am using the startxwin.sh script from the distribution (unmodified) to start Xwin in multiwindow mode. Should I specify some optional parameters or is this a known problem ? -- Richard Gourdeau
Re: invalid Window parameter error through ssh X forwarding
Replace 'ssh -X' with 'ssh -Y'. Harold Richard Gourdeau wrote: I have just upgraded my xfree-cygwin setup (Xwin serv Release 4.3.0-64, etc.). Some apps that worked through ssh without any problem with my previous setup (Xwin serv Release 4.3.0-58, etc.) are now exiting with errors messages related to an invalid Window parameter. For example, in a xterm after an ssh connect with X forwarding, gftp starts but as soon as I try to select a menu item, I get the following error: === [EMAIL PROTECTED] gourdeau]$ gftp [1] 13684 [EMAIL PROTECTED] gourdeau]$ Gdk-ERROR **: BadWindow (invalid Window parameter) serial 3647 error_code 3 request_code 38 minor_code 0 Gdk-ERROR **: BadAccess (attempt to access private resource denied) serial 3648 error_code 10 request_code 102 minor_code 0 [1]+ Exit 1 gftp === I have notice that the mouse cursor remains as an X and does not change to an arrow when moved over the gftp application. I am using the startxwin.sh script from the distribution (unmodified) to start Xwin in multiwindow mode. Should I specify some optional parameters or is this a known problem ?
SSH X forwarding not working
Greetings. I've looked over the mailing list, but haven't been able to find out why using ssh -X remote-host wouldn't actually let you run X apps on the distant machine (to display locally). I'm using the absolute latest and greatest Cygwin XFree86 (fetched yesterday). Any help would be much appreciated. NOTE: I use startx (I have also tried using xinit) and have added 'export DISPLAY=localhost:0.0' to my .xinitrc. Thanks in advance. chris. - [EMAIL PROTECTED] 703.413.1100 x5100
Re: SSH X forwarding not working
Viestissä Torstai 6. Maaliskuuta 2003 23:04, Chris Horn kirjoitti: Greetings. I've looked over the mailing list, but haven't been able to find out why using ssh -X remote-host Have you configured the remote end to accept X forwarding in /etc/ssh/sshd_config? -- /(anton)
Re: SSH X forwarding not working
/ Chris Horn [EMAIL PROTECTED] wrote: | Greetings. I've looked over the mailing list, but haven't been able | to find out why using | | ssh -X remote-host Try to throw on one or two -v's to check what ssh thinks. From where do you do ssh -X remote-host, and what is the value of the variable $DISPLAY at the prompt before ssh, and the prompt at the other end when the ssh is connected. What does the apps say in the other end when you try to start them? /Andy -- The eye of the beholder rests on the beauty!
Re: SSH X forwarding not working
At the other end, /etc/ssh/sshd_config now has the line X11Forwarding yes Still no go. When I connect, the DISPLAY value on the remote box appears null. When I'm local, it's localhost:0.0 The error I receive when trying to run apps is Gtk-WARNING **: cannot open display: When I used xhost and set DISPLAY manually, things work: 1. xhost +remote_host 2. on remote box set DISPLAY to local_host:0.0 3. run app, and it appears like it should! Also, does anyone know how to cut and paste: 1. Within X (do I have to run XWin with -emulate3buttons?), and 2. between X and Windows? Merci beaucoup. chris. At 04:02 PM Thursday 3/6/2003, you wrote: viestissä torstai 6. maaliskuuta 2003 23:04, chris horn kirjoitti: greetings. i've looked over the mailing list, but haven't been able to find out why using ssh -x remote-host have you configured the remote end to accept x forwarding in /etc/ssh/sshd_config? -- /(anton) - [EMAIL PROTECTED] 703.413.1100 x5100
Re: SSH X forwarding not working
Chris, Okay, so you had X11Forwarding disabled before. What have you done to make sshd re-read its configuration file? Specifically restarted sshd? Restarted the entire machine? What? I suspect that sshd happily thinks that X11Forwarding is still disabled. Harold Chris Horn wrote: At the other end, /etc/ssh/sshd_config now has the line X11Forwarding yes Still no go. When I connect, the DISPLAY value on the remote box appears null. When I'm local, it's localhost:0.0 The error I receive when trying to run apps is Gtk-WARNING **: cannot open display: When I used xhost and set DISPLAY manually, things work: 1. xhost +remote_host 2. on remote box set DISPLAY to local_host:0.0 3. run app, and it appears like it should! Also, does anyone know how to cut and paste: 1. Within X (do I have to run XWin with -emulate3buttons?), and 2. between X and Windows? Merci beaucoup. chris. At 04:02 PM Thursday 3/6/2003, you wrote: viestissä torstai 6. maaliskuuta 2003 23:04, chris horn kirjoitti: greetings. i've looked over the mailing list, but haven't been able to find out why using ssh -x remote-host have you configured the remote end to accept x forwarding in /etc/ssh/sshd_config? -- /(anton) - [EMAIL PROTECTED] 703.413.1100 x5100
Re: SSH X forwarding not working
Hmm looked through the mail again and saw: | ssh -x remote-host Have you tried ssh -X, capital X, using small x disables ssh forwarding. Meanwhile: / Chris Horn [EMAIL PROTECTED] wrote: | At the other end, /etc/ssh/sshd_config now has the line X11Forwarding yes | | Still no go. | | When I connect, the DISPLAY value on the remote box appears null. | When I'm local, it's localhost:0.0 And this local, it is from the prompt you do ssh from? | When I used xhost and set DISPLAY manually, things work: just a note, you are aware that the X traffic goes unencrypted when doing it this way (setting DISPLAY to host_done_ssh_from)? | 2. on remote box set DISPLAY to local_host:0.0 Assuming local_host here is host_done_ssh_from? | Also, does anyone know how to cut and paste: | 1. Within X (do I have to run XWin with -emulate3buttons?), and If you have a threebutton mouse like microsoft with scrollball, you probably can use the third button.. (like me) | 2. between X and Windows? There are work being done on this, check the mailinglist. xwinclip is the keyword I think. /Andy -- The eye of the beholder rests on the beauty!
Re: SSH X forwarding not working
I had restarted sshd. At 04:45 PM Thursday 3/6/2003, you wrote: Chris, Okay, so you had X11Forwarding disabled before. What have you done to make sshd re-read its configuration file? Specifically restarted sshd? Restarted the entire machine? What? I suspect that sshd happily thinks that X11Forwarding is still disabled. Harold Chris Horn wrote: At the other end, /etc/ssh/sshd_config now has the line X11Forwarding yes Still no go. When I connect, the DISPLAY value on the remote box appears null. When I'm local, it's localhost:0.0 The error I receive when trying to run apps is Gtk-WARNING **: cannot open display: When I used xhost and set DISPLAY manually, things work: 1. xhost +remote_host 2. on remote box set DISPLAY to local_host:0.0 3. run app, and it appears like it should! Also, does anyone know how to cut and paste: 1. Within X (do I have to run XWin with -emulate3buttons?), and 2. between X and Windows? Merci beaucoup. chris. At 04:02 PM Thursday 3/6/2003, you wrote: viestissä torstai 6. maaliskuuta 2003 23:04, chris horn kirjoitti: greetings. i've looked over the mailing list, but haven't been able to find out why using ssh -x remote-host have you configured the remote end to accept x forwarding in /etc/ssh/sshd_config? -- /(anton) - [EMAIL PROTECTED] 703.413.1100 x5100 - [EMAIL PROTECTED] 703.413.1100 x5100
Re: SSH X forwarding not working
At 04:50 PM Thursday 3/6/2003, you wrote: Hmm looked through the mail again and saw: | ssh -x remote-host Have you tried ssh -X, capital X, using small x disables ssh forwarding. Sorry, sloppy typing. I've been using -X, the text in this email was a typo. Meanwhile: / Chris Horn [EMAIL PROTECTED] wrote: | At the other end, /etc/ssh/sshd_config now has the line X11Forwarding yes | | Still no go. | | When I connect, the DISPLAY value on the remote box appears null. | When I'm local, it's localhost:0.0 And this local, it is from the prompt you do ssh from? Yeah. When I'm in Cygwin XFree86 on my local machine in an xterm, I've been typing 'echo $DISPLAY' to see what it's set to. | When I used xhost and set DISPLAY manually, things work: just a note, you are aware that the X traffic goes unencrypted when doing it this way (setting DISPLAY to host_done_ssh_from)? Yes. Which is why I want to get SSH's X forwarding working already! | 2. on remote box set DISPLAY to local_host:0.0 Assuming local_host here is host_done_ssh_from? Yeah. I was on the remote machine (through a SSH session) and set DISPLAY to be the display of the machine I'm sitting at - which I've been calling local (because it's right in front of me). Sorry, I guess I could've been clearer. | Also, does anyone know how to cut and paste: | 1. Within X (do I have to run XWin with -emulate3buttons?), and If you have a threebutton mouse like microsoft with scrollball, you probably can use the third button.. (like me) Huh. I think the problem is that I have the middle mouse button (the scrollwheel) set to double-click in Windows and that behavior is overriding what it would normally do in X - namely paste! I exclusively run Linux on my personal machine at home, so not having paste is *really* frustrating! | 2. between X and Windows? There are work being done on this, check the mailinglist. xwinclip is the keyword I think. I'll check it out; thanks. - [EMAIL PROTECTED] 703.413.1100 x5100
X forwarding from Windomaker menu item (problem)
I just recently upgraded to Win2K from WinNT. In doing so, I also upgraded to the latest and greatest cygwin release. After doing this, everything works fine (most things better) accept for my X forwarding of apps via menu items from WindowMaker. Here is how I have my environment set up: First I start X with ssh-agent, and use ssh-add to authenticate to the agent. I have menu items in windowmaker that look like: ssh -X user@unix box some X program. I use this to run various things, usually off a Linux box. This worked fine until I upgraded. If I issue the above command from an xterm, it works. I've run sshd in debug mode as well as the client redirecting the output to a file and according to the output, the commands work and the X programs are forwarding somewhere, but they don't show up on my local display for some reason. I have to go kill them on the remote machines too, they don't die when I shut down X locally. The only thing I see that is different (other than the obvious version differences) is I get the following now on any X forwarding session: Warning: No xauth data; using fake authentication data for X11 forwarding. But I get that even when the X Forwarding works. Attached is some output from sshd runing netscape off a sun box. Anybody with a clue, please help. I'm plum out of cluefulness. R. Marc debug1: sshd version OpenSSH_3.4p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA debug1: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22. Generating 768 bit RSA key. RSA key generation complete. debug1: Server will not fork when running in debugging mode. Connection from 1.1.1.5 port 2187 debug1: Client protocol version 2.0; client software version OpenSSH_3.5p1 debug1: match: OpenSSH_3.5p1 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-1.99-OpenSSH_3.4p1 debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: client-server aes128-cbc hmac-md5 none debug1: kex: server-client aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent debug1: dh_gen_key: priv key bits set: 121/256 debug1: bits set: 1557/3191 debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT debug1: bits set: 1551/3191 debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: KEX done debug1: userauth-request for user someuser service ssh-connection method none debug1: attempt 0 failures 0 debug1: Starting up PAM with username someuser debug1: PAM setting rhost to 1.1.1-5.somedomain.com Failed none for someuser from 1.1.1.5 port 2187 ssh2 debug1: userauth-request for user someuser service ssh-connection method publickey debug1: attempt 1 failures 1 debug1: test whether pkalg/pkblob are acceptable debug1: temporarily_use_uid: 100/100 (e=0) debug1: trying public key file /export/home/someuser/.ssh/authorized_keys debug1: restore_uid debug1: temporarily_use_uid: 100/100 (e=0) debug1: trying public key file /export/home/someuser/.ssh/authorized_keys2 debug1: matching key found: file /export/home/someuser/.ssh/authorized_keys2, line 1 Found matching DSA key: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 debug1: restore_uid Postponed publickey for someuser from 1.1.1.5 port 2187 ssh2 debug1: userauth-request for user someuser service ssh-connection method publickey debug1: attempt 2 failures 1 debug1: temporarily_use_uid: 100/100 (e=0) debug1: trying public key file /export/home/someuser/.ssh/authorized_keys debug1: restore_uid debug1: temporarily_use_uid: 100/100 (e=0) debug1: trying public key file /export/home/someuser/.ssh/authorized_keys2 debug1: matching key found: file /export/home/someuser/.ssh/authorized_keys2, line 1 Found matching DSA key: 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 debug1: restore_uid debug1: ssh_dss_verify: signature correct Accepted publickey for someuser from 1.1.1.5 port 2187 ssh2 debug1: Entering interactive session for SSH2. debug1: fd 7 setting O_NONBLOCK debug1: fd 8 setting O_NONBLOCK debug1: server_init_dispatch_20 debug1: server_input_channel_open: ctype session rchan 0 win 131072 max 32768 debug1: input_session_request debug1: channel 0: new [server-session] debug1: session_new: init debug1: session_new: session 0 debug1: session_open: channel 0 debug1: session_open: session 0: link with channel 0 debug1: server_input_channel_open: confirm session debug1: server_input_channel_req: channel 0 request x11-req reply 0 debug1: session_by_channel: session 0 channel 0 debug1: session_input_channel_req: session 0 req x11-req debug1: bind port 6010: Address already in use debug1: bind port 6011: Address
RE: ssh x forwarding
This probably should have been on the xfree list. From: Patrick Nelson [mailto:[EMAIL PROTECTED]] In ssh you get x forwarding. But, I can't seem to get it working. A command like: ssh -l user system x app always responds with something like: Gtk-WARNING **: cannot open display: Is there some configuration that needs to take place in cygwin first? Yes I can log in by dropping the x app part and yes the x app is available. Tried running the above from a terminal that displayed after doing a startx too... same result. So I have to figure I just don't have something setup correctly. At a minimum, you need to have the DISPLAY variable set before you execute the ssh, and you need to use the X forwarding (-X) option to ssh so: export DISPLAY=localhost:0.0 ssh -X -l user system x app -Richard Campbell.
