Ok I just tested this (something different) from an Ubuntu VM on my laptop to my Arch server in the other room
I started by trying: ssh -Y 192.168.0.2 it gave me a message: X11 forwarding request failed on channel 0 , and logged me into the machine without x so I Edited /etc/ssh/sshd_config file: $ sudo vi /etc/ssh/sshd_config and set the following two options: X11Forwarding yes X11UseLocalhost no and then I sudo systemctl reload sshd then logged out, then I was able to ssh -Y 192.168.0.2 and I successfully launched deepin-terminal incidentally, when I: echo $DISPLAY on the deepin-terminal it returns serverName:10.0 also, xorg-xauth is installed on the server On Thu, Jan 3, 2019 at 10:39 AM John Meissen <j...@meissen.org> wrote: > > biob...@gmail.com said: > > In my experience, I need to be logged into X on the machine I'm ssh -Xing > > into, and then you need to (you could also add this to your .bashrc file) > > > export DISPLAY=:0.0 > > That would be very much the wrong thing to do, and would break things. > > Set up correctly, the ssh server sets up a different socket on the remote > system to act as a tunnel to the machine you're coming from. So, for > instance, > from one of my ssh sessions: > > $ echo $DISPLAY > localhost:14.0 > > If it's not working then you still have the ssh client or server > configured > wrong. > > > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
