logoalt Hacker News

nixosbestostoday at 1:10 AM3 repliesview on HN

Accessibility? Sure. Everything else? Nah, I'm sorry. There are countless ways to do remoting with Wayland. There are countless ways to do kb+mouse sharing.


Replies

MrDrMcCoytoday at 5:51 AM

I love Wayland a lot, but as far as I can tell the available remoting solutions still cannot enable a headless LXC container to serve a KDE Plasma Wayland desktop. I spent the last couple days trying to cobble some solution together for it and failed miserably. If you know a way, I would be most grateful :-)

show 1 reply
lelanthrantoday at 7:11 AM

> There are countless ways to do kb+mouse sharing.

Wait, what? I tried this last year. I didn't find any way to do this that wasn't dependent on the WM.

superkuhtoday at 2:15 AM

>There are countless ways to do kb+mouse sharing.

You realize that's worse, right? And to be clearer: core Wayland protocol does not have countless ways. It has zero.

Instead of a single protocol with the strong X11 reference X server the wayland compositors pick and choose between libinput, or libei, or libportal with the InputCapture PR, xdg-desktop-portal with the InputCapture interface, some I've probably missed, or maybe you have nothing at all (weston). It's a gamble if your choice of desktop environment and it's wayland compositor's non-core wayland protocols will match up with those the developer for $software chose. On X11 linux everything that works somewhere works everywhere. With the various waylands if you stay within your desktop's ecosystem you'll probably not notice, but go beyond it and you will.

Each wayland desktop pretty much runs it's own compositor with it's own set of third party libs because the wayland core protocol spec is very minimal. I would say incomplete. ref: https://wayland.app/protocols/

show 1 reply