any one get ssh x11 forwarding working

[risingsunxy]

hi guys,
has anyone successfully got the ssh x11 forwarding working?
in /etc/ssh/sshd_config
X11Forwarding yes
X11DisplayOffset 10

the DISPLAY is also set to my desktop

ssh -X is also used to login.
but still got the can not open display error, e.g., gvim
E233: cannot open displayE852: The child process failed to start the GUI
Press ENTER or type command to continue

midori
Midori - Cannot open display:

any ideas to get this to work?

thanks a lot!

[gazmandev]

I have this working on a OSX laptop. I haven't actually done anything other than what you've done. I do find however that if I'm logged in and idle for a while, I need to log out and back in for it to get back into action - Midori will report that error message your getting. Also, some windows will not open regardless (I know gparted refuses to open at all over SSH).

If you're using Windows, you will need to use something that has a X Server/Client. Putty won't cut it. I haven't been successful in getting X working over SSH in Windows using the Pi or any other version of Linux.

[Heater]

On my stock raspian I have not changed any configs for ssh or X. I get X forwarded to my Debian PC with just the ssh -X.... command.

[PIstolero]

X11 forwarding is already enabled on the raspian image. To get it working on Windows I just installed Xming as Xserver and used putty to launch an X app

[risingsunxy]

my desktop is a Ubuntu 12.04 PC.
I also tried to xhost+, but still not working....

[marosg]

Worked for me without any configuration.

Maybe it would help if you ssh -X to raspbian and post
1. echo $DISPLAY
2. actual copy/paste error from running midori or lnxterm

[risingsunxy]

after login, echo $DISPLAY
got nothing
then I export DISPLAY=192.168.1.66:10 (my desktop ip)
$gvim

E233: cannot open displayE852: The child process failed to start the GUI
Press ENTER or type command to continue


$midori


Midori - Cannot open display:

[Joe Schmoe]

With the caveat that it should, of course, "just work", I have to ask:

Is there any reason to go the "X forwarding" route, as opposed to going the VNC route?
The VNC route seems a lot cleaner and normal-er to me.

[risingsunxy]

Now I got it working on my windows after a little bit hacking of the xming (put -ac options in xming shortcut).

but still not working on the ubuntu side.

I think this at least mean the config on pi is ok, should be my ubuntu side 's issue.

[PIstolero]

With X forwarding I can have a single application on my remote box, with VNC I have the complete GUI on my remote box. I would not say that one is better as the other, it is just different.

[marosg]

On Ubuntu you have to allow remote connection coming. Issue "xhost +" (of course more secure is to specify just single IP)

[marosg]

With the caveat that it should, of course, "just work", I have to ask:

Is there any reason to go the "X forwarding" route, as opposed to going the VNC route?
The VNC route seems a lot cleaner and normal-er to me.

VNC starts the whole X server, so it consumes more CPU cycles. X forwarding is always there, while you have to install VNC.

But of course for many circumstances VNC is better, it depends on your needs.

[JosephRedfern]

I had this issue, too. I had previously removed everything to do with X11/xserver/xorg - I thought by re-installing X I'd be good to go in terms of X11 forwarding, but it turns out not.

I ran:

Code: Select all

sudo apt-get install xauth

and now all is well.

[TillM]

Works perfectly for me from my debian box to rasbian.
I just ssh -l USERNAME -X RAS_IP /YOUR/PROGRAM/YOU/WANT/TO/RUN

[wanderer]

Working from mint 13 to raspbian using putty. Under Connections--> X11 set "X display location" to localhost:0 . Test with xclock & to see if working.

[tobiz]

Working from mint 13 to raspbian using putty. Under Connections--> X11 set "X display location" to localhost:0 . Test with xclock & to see if working.

It would be most useful to say on which machine of mint 13 and the raspi you do this; it's not very clear from your post (don't assume it's obvious).

[HJ_SK]

Now I got it working on my windows after a little bit hacking of the xming (put -ac options in xming shortcut).

but still not working on the ubuntu side.

I think this at least mean the config on pi is ok, should be my ubuntu side 's issue.

Thanks! This is a nice solution for me!