Hi, there's no sense in using x2gokdrive or x2goagent/nxagent with Wayland because both are X servers. You can use them today (for applications "speaking" X only) by using the Xwayland on the client, since that is where the resulting X protocol messages need to be handled. Pure Wayland applications will not work with this setup (although I don't even know if such applications exist at all). https://unix.stackexchange.com/questions/482129/can-i-run-wayland-application-in-x states that Weston is able to work as a proxy between wayland apps and X11.
So AFAIU a solution with Waypipe would be something completely different where x2go only handles the session management. I have tried to put this into a table (AFAIU). In || I list the the used protocol: X: standard X11 protocol NX: nx compressed protocol WL: Wayland WP: Waypipe XK: x2gokdrive protocol XS: X11 tunneled through ssh These are the possible communications ways: Server Client 1 XApp |X11| Xserver 2 XApp |X11| sshd |XS| ssh |X11| Xserver 3 XApp |X11| nxagent |NX| nxproxy |X11| Xserver 4 XApp |X11| x2gokdrive |XK| x2gokdriveclient |X11| Xserver 5 XApp |X11| nxagent |NX| nxproxy |X11| Xwayland |WL| Wayland 6 XApp |X11| x2gokdrive |XK| x2gokdriveclient |X11| Xwayland |WL| Wayland 7 WaylandApp |WL| Waypipe |WP| Waypipe |WL| Wayland 8 WaylandApp |WL| Weston |X11| nxagent |NX| nxproxy |X11| Xserver 9 WaylandApp |WL| Waypipe |WP| Waypipe |WL| Weston |X11| Xserver So we have to setup anything on the server that outputs one of the four protocols: XS, NX, XK, WP. On the client side we have to route these four protocols to either display them on an Xserver or a Wayland server. The less components between app and server the better the experience. But to support both server types and both app types there are some compromises required. I am not into any Wayland or Waypipe stuff, so correct me if I'm wrong. Uli
_______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
