On Sunday 27 November 2016 13:49:17 Peter Stuge wrote:> Gene Heskett wrote: > > > On pi, in same shell as above, start the GUI application > > > > So the monitor is plugged into the droid, but the keyboard & mouse > > are plugged into the pi? > > No; X11 is a remote windowing protocol. Monitor, keyboard and mouse > are connected where your X server runs. > > Applications run on the network and their windows display on the X > server. > > > ssh login > > There seems to be no reason to use SSH. > > > If all this can be put into the correct rc.local files > > Set environments correctly and then start X server on one system and > the application on the other system. >The odroid64 already has an x system running as soon as I log into the odroid64. Its $DISPLAY is :0 I'm at a dead end, I think I have all the i's dotted and the t's crossed but I cannot get a single byte across the link because the pi cannot open the display on the odroid64. I suspect it may be the display number, which is :0 on the instance running on the odroid46, automaticly brought up when I log into the odroid64. and an echo $DISPLAY on the pi shows: (after I've done the commands) 192.168.71.9:0 I have a hunch that is the error. Or at least the next hurdle. The .Xauthority file on both machines had grown to several kilobytes, so I blew them away, then discovered I needed to touch them, x couldn't create the missing file. I figured I'd start with a clean slate on both SBC's that way. And I did get a round tuit and put a power cord in the two pads next to that worthless coax connector, so now the odroid64 has solid power. Finally. Thanks Peter.> //Peter > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-devCheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Gene Heskett wrote:> The odroid64 already has an x system running as soon as I log into > the odroid64. Its $DISPLAY is :0That's fine. Remember to run xhost +192.168.71.pi on odroid64.> the pi cannot open the display on the odroid64.Show an error message when starting e.g. xterm on pi.> an echo $DISPLAY on the pi shows: (after I've done the commands) > 192.168.71.9:0If the odroid IP is 192.168.71.9 then that is correct. Way off topic now. //Peter
On 11/27/2016 5:21 PM, Peter Stuge wrote:> Gene Heskett wrote: >> The odroid64 already has an x system running as soon as I log into >> the odroid64. Its $DISPLAY is :0 > > That's fine. Remember to run xhost +192.168.71.pi on odroid64. > > >> the pi cannot open the display on the odroid64. > > Show an error message when starting e.g. xterm on pi. > > >> an echo $DISPLAY on the pi shows: (after I've done the commands) >> 192.168.71.9:0That looks like the local display in the pi but you said it has no monitor is attached. If you ran ssh on odroid64 and had the X11 Forwarding correct, the sshd on pi will set up an X proxy on pi and set DISPLAY=localhost:10.0 for the first user and pass this to the user in the environment On the pi you also need /etc/ssh/sshd_config: X11Forwarding yes X11DisplayOffset 10 If you have a ~/.ssh/rc file on the pi you may need to add code to process the cookie and set the DISPLAY. See the man ssh on the pi,. look for DISPLAY This is done before the login shell, so you must not set the DISPLAY again in your login files. Just ran some tests using my old pi from 2013: Linux raspberrypi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux OpenSSH_6.0p1 Debian-4+deb7u2, OpenSSL 1.0.1e 11 Feb 2013 SSh from Windows 10 using PuTTY, with Xming. From a Ubuntu-16.4 VM to the pi using ssh -l user -X ip-address-of-pi the display gets set as DISPLAY=localhost:11.0 /usr/bin/X11/xev on the pi is a good test program. or x-terminal-emulator For performance you may want to google for: "X windows" performance ssh> > If the odroid IP is 192.168.71.9 then that is correct. > > > Way off topic now. > > > //Peter > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev >-- Douglas E. Engert <DEEngert at gmail.com>
On Sunday 27 November 2016 18:21:00 Peter Stuge wrote:> Gene Heskett wrote: > > The odroid64 already has an x system running as soon as I log into > > the odroid64. Its $DISPLAY is :0 > > That's fine. Remember to run xhost +192.168.71.pi on odroid64. > > > the pi cannot open the display on the odroid64. > > Show an error message when starting e.g. xterm on pi. > > > an echo $DISPLAY on the pi shows: (after I've done the commands) > > 192.168.71.9:0 > > If the odroid IP is 192.168.71.9 then that is correct.It is.> > Way off topic now.Not really, its getting closer to what I wanted to do when I started this thread. What I wanted to do was bypass the ssh's encrypt/decrypt time killers. But another network savvy fellow on the emc list says I should get the display by running this on the pi: xauth extract - $DISPLAY|ssh <pi-usr>@<raspi-ip> xauth merge - which does not update the $DISPLAY var on the pi, it remains at at localhost:10 This was the actual command line: gene at raspberrypi:~ $ xauth extract - $DISPLAY|ssh gene at 192.168.71.9 xauth merge - gene at 192.168.71.9's password: gene at raspberrypi:~ $ echo $DISPLAY localhost:10.0 This lack of apparent effect is possibly an artifact of my being logged into both SBC from a 3rd (this machine) source. Thank you Peter. Got to get more sleep tonight. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>