5 ms·
X forwarding "just works" in Wayland via XWayland. None of that has changed significantly. But I'm disappointed to see this myth keep popping up. X in general
by md8z 5y ago
X forwarding "just works" in Wayland via XWayland. None of that has changed significantly.
But I'm disappointed to see this myth keep popping up. X in general isn't "network transparent." Some X11 clients are, but only if they're built in a very specific way, which also tends to degrade performance locally.
- buovjaga 5y agoThanks for the effort you are putting into comments here lately! Maybe you have ideas on improving the "Are we Wayland yet?" site: https://github.com/mpsq/arewewaylandyet https://github.com/mpsq/arewewaylandyet Yesterday I sent a PR for a "Missing" section.
- md8z 5y agoThere isn't much for me to say. To be honest, I would probably not contribute to that website. Wayland isn't that exciting of a technology and I don't think end users should even need to care about it or care that any of those utilities supports Wayland, if distro developers are doing their jobs then it will all "just work" and nobody has to worry about it. Also that website is misleading, many of those utilities are wlroots specific and not really useful on other implementations.
- rbanffy 5y agoIt may be an Ubuntu issue then. I’ve tried to start gnome-terminal on the Linux laptop from the Mac running XQuartz and what happened was a terminal starting on my screen on the Linux box, totally ignoring I was sshing into the Linux machine from the Mac.
- md8z 5y agoMaybe you were using the wayland backend, you might have to force X11 with the environment variable "GDK_BACKEND=x11". Though part of this weirdness is due to the clunkiness of the way X forwarding is implemented, I wish there was a way to do it that didn't involve kludging around with environment variables. But that is what we are stuck with.