hid-xpadneo: Revoke hidraw user access to fix a Proton mapping problem

Proton seems to have a special handling for SDL HID devices which, when HIDAPI is used, re-exports the controller under a crafted SDL GUID. This messes up the mappings in all Proton games tested so far. Only recent Proton versions may be affected. So let's temporarily revoke user access from hidraw devices until the issue is resolved. Thanks to https://github.com/ivyl from CodeWeavers for helping in uncovering this issue. See-also: ValveSoftware/Proton#4707 Signed-off-by: Kai Krakow <[email protected]>
atar-axis · Apr 3, 2021 · f7e1e8a · f7e1e8a
1 parent 0151f36
commit f7e1e8a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/hid-xpadneo/etc-udev-rules.d/60-xpadneo.rules b/hid-xpadneo/etc-udev-rules.d/60-xpadneo.rules
@@ -1,2 +1,2 @@
 ACTION=="add", KERNEL=="0005:045E:02FD.*|0005:045E:02E0.*|0005:045E:0B05.*|0005:045E:0B13.*", SUBSYSTEM=="hid", DRIVER!="xpadneo", ATTR{driver/unbind}="%k", ATTR{[drivers/hid:xpadneo]bind}="%k"
-ACTION=="add|change", DRIVERS=="xpadneo", SUBSYSTEM=="hidraw|input", TAG+="uaccess"
+ACTION=="add|change", DRIVERS=="xpadneo", SUBSYSTEM=="input", TAG+="uaccess"