steam-devices VS barrier

if you mean this ( https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules ) in /etc/udev/rules.d , yes i did

Create an udev rule for the device, you can copy the rule for your device from here.

I am attempting to play Spelunky with a controller but I am not having any luck. Spelunky has a platinum rating on protondb and runs as expected. I am in a flatpak and I did install the udev rules from valve if any of that makes a difference. My controller works fine in native games.

I solved the problem by copying the 60-steam-input.rules file to the folder: /etc/udev/rules.d

this is their Github: https://github.com/ValveSoftware/steam-devices

steam maintains udev rules for controllers that might help: https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules

Here is my open PR for the hori alpha for reference: https://github.com/ValveSoftware/steam-devices/pull/42/files

To use a controller with the Steam flatpak, you need to layer the steam-devices package from RPM Fusion, or download the udev rules from upstream and install them to /etc/udev/rules.d/ (which is what I did).

> The effort you need to go through to actually use these depends on how your distribution handles the file permissions of /dev/uinput. Some of them have it as root:input, in which case you just need to usermod -a -G input and then relog to get it working. Others have it as root:root so you either need to go do some reconfigurations to change its permissions or live with running the software using it as root.

There's a trick to that. The TL;DR is "install the steam-devices package or similar" (https://github.com/ValveSoftware/steam-devices/), which adds the following udev rule (and others, but this is the relevant one):

  # Steam Controller udev write access

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.