wlroots-eglstreams VS barrier

I actually got a chance to develop against some proprietary API and i don't blame them for not wanting to support proprietary drivers , But there is at least one guy maintaining a fork for nvidia so you can try your luck there.

The developer of the EGL stream fork of wlroots wants to migrate to the original version, maybe if he will become a maintainer there could be a change in the status quo, or he can maintain a fork with fixes.

Sway uses wlroots, which is one of I believe 3 wayland libraries (wlroots, smithay and taiwins). It just happens that sway (and most other compositors such as river, hikari, dwl) use wlroots, which doesn't care about nvidia. There is wlroots-eglstreams if you want to try that.

That is not entirely true, there is a fork of wlroots which supports NVIDIA's proprietary driver's EGLStreams implementation, which works fine with Sway and probably other WMs too, see https://github.com/danvd/wlroots-eglstreams.

In the meantime you can use wlroots-eglstreams

Install a fork of wlroots (the library used by Sway to do pretty much everything).

Also I know about a fork a guy did for wlroots that adds support for egl streams but this is far from ideal, it's a interesting job nonetheless https://github.com/danvd/wlroots-eglstreams

If your a technical person , you can give wlroots-eglstreams a try (it's a fork of wlroots adding nvidia support).

As of now you can run Sway with wlroots-eglstreams, which is a work-in-progress fork of wlroots, working as drop-in replacement, see https://github.com/danvd/wlroots-eglstreams and https://aur.archlinux.org/packages/wlroots-eglstreams-git/.

For software KVM you can use https://github.com/debauchee/barrier

I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)

libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?

For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through

And for host systems, it looks like xev only logs input events when the window is focused.

Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?

With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.

Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier

libei:

I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.

Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...

Barrier appears to handle PC switching only for the keyboard and mouse.

Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.

Barrier is a free and open source alternative.