evsieve VS barrier

Same with evsieve: I can see the keys I press, like in wev, but the remap doesn't work for the keyboard or the mouse:

My best suggestion for you is to leverage evsieve: https://github.com/KarsMulder/evsieve

There are many other software tools such as https://github.com/jtroo/kanata and https://github.com/KarsMulder/evsieve. The main difference with 𝑥MK is that you can use native QMK and ZMK.

Ironically I know you can do this in i3 and xorg/gnome using xmodmap or editing the xkb file. I'm pretty sure wayland compositors should be able to read xkb-compliant files but the recommended way of loading that in is probabaly different between various compositors? You could also use a "second generation" interception tool that works at the event device level.

You might want to try evsieve, it even has an example about toggling devices and it concludes with a hint on how to get this to work for 2 VMs.

Evsieve is amazing in general you sould check it out 🙂

evsieve has solved that for me, as the virtual device created is always available; it starts when I log on my computer and stay open forever.

evsieve can remap. I haven't used it yet but you can find it here: https://github.com/KarsMulder/evsieve

If this feels a bit limited (you have a few predefined options), there's also evsieve. Which allows you to do a lot more (like selective key pass-through, shortcuts, etc.).

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.