ah I did not see your previous post.
IMHO the big disadvantage is that you can´t move the 2nd Xwayland session, can you? It’s fixed. Unless you want a kiosk using 100% of the desktop.
Update: Xwayland -decorate
… I am pretty sure there is a way to put that extra Xsession in a movable window … with Wayland in the mix I would need to do a bit of experimenting/reverse engineering/damage additional brain cells that are in short supply to figure it out … LOL!!!
And I JUST saw your next post LOL!!! yup, that works 
So, for the benefit of closing the loop …
- install a window manager — we used fvwm
- Xwayland :10 -decorate -ac -geometry 1024x768 -listen tcp & ---- start another Wayland aware Xsession at display :10
- fvwm -d :10 & ---- attach the fvwm to display :10
- (optional) xterm -d {IPaddress:10} ---- start an Xclient in the Xsession at :10
- have the remote Xclient (the Motorola) connect to this Xserver …
Done
Looks pretty good, window is movable/relocatable, works in a Wayland session and fairly simple to script/do …
(Amazing what 2 old propeller-heads can accomplish … LOL!!!)
What do you think Michael?
(one small caveat … if using ssh X11 forwarding, you might want to put this Xsession on a different display, like :5 or :20 )
you can maybe skip the window manager, but it depends on what kind of window the client is creating. If it’s a window with a fixed size, then start the xwayland session with this geometry and be done with it.
1 Like
Yes, running the additional instance of Xwayland works (if I add the +byteswappedclients option) with fvwm (to get the mouse to work).
I think that might be a little more complicated and than the socat pipe.
However, I do now have several viable solutions and have a much better understanding of X windows with wayland.
Thanks all for the help!
4 Likes
Would it be more accurate to say " ---- start another Wayland Xsession aware display
at display :10"
LOL … TomAto, Tomato … LOL
Welcome to Fedora Papa Charlie …
1 Like
More like AtoTom . . . TomAto . . .
It just helps me wrap me head around what is going on . . .
… yeah … with X that’s always been the case … LOL!!!
What I am trying to say is that Xwayland is designed to work with Wayland so both components are actually aware of each other … if that makes more sense …
Xwayland knows that Wayland most likely already has control of DISPLAY :0 , the console basically … so if you start another Xsession via Xwayland AND tell it to be DISPLAY > :0 , it will not complain …
1 Like
So for a very long time, I’ve had a severe grudge against Wayland, believing that it killed the “-X” option to ssh. I kept the -X option in commands out of habit. Had to jump through hoops ( Ctl + Alt + Fx, login, run xinit, login to remote system and complete the task, then kill the session and Ctl + Alt + Fx back to my original session or use Xnest which is a bit more bearable etc etc) if I needed to run something on a remote system that opens a graphical window. I was pleasantly shocked a few days ago when I did “ssh -X me@SomeServerOnTheInternet xeyes” expecting to get an error but xeyes popped up on my screen . . . Previously, I would need to logout of the Wayland session and pick an Xorg session from the login screen and login again to be able to do this . . .