4 ms·

Now do it with Xwayland, any differences?

• tverbeure 3y ago
  I don't know anything about Xwayland, but there's this sentence in this socat writeup: > If you want to access an X server that does not provide -listen tcp (Xwayland) or just did not have enabled it during startup (like most likely your host Xorg), you can use socat to provide TCP/IP access. https://github.com/mviereck/x11docker/wiki/How-to-access-X-over-TCP-IP-network#socat-tcpip-setup https://github.com/mviereck/x11docker/wiki/How-to-access-X-o... This makes me think that socat is exactly what you need to make it work with Xwayland?
  • hsbauauvhabzb 3y ago
    In my experience, a dedicated virtual machine running $problematic_stack often beats any workarounds - there’s often not enough people power to make niche workarounds like that work well, sometimes they’re brilliant, other times they’re barely functional.
    • tverbeure 3y ago
      I’m OK with barely functional if it works for me! These blog posts are about not forgetting how I did something when I need to build the setup again in the future. Google is better at searching the web than at searching local notes on one of my machines. :-)
      • hsbauauvhabzb 3y ago
        Oh to be clear, I’m referring to wayland w/ x forwarding and I probably worded my comment poorly - point is sometimes I wont invest time when something obscure doesn’t work and other times if it’s obscure I’ll use some other workaround that avoids obscurity as much as possible. There are some pretty good ‘hacks’ that work brilliantly (sshfs for example) and others which work terribly (nvidia binary drivers seem to keep failing on me to the point where buying an AMD card may have a better ROI)
• yjftsjthsd-h 3y ago
  It's probably exactly the same?