Search Criteria
Package Details: game-devices-udev 0.16-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/game-devices-udev.git (read-only, click to copy) |
|---|---|
| Package Base: | game-devices-udev |
| Description: | Udev rules for controllers |
| Upstream URL: | https://gitlab.com/fabiscafe/game-devices-udev |
| Licenses: | MIT |
| Submitter: | fabiscafe |
| Maintainer: | fabiscafe |
| Last Packager: | fabiscafe |
| Votes: | 4 |
| Popularity: | 0.62 |
| First Submitted: | 2021-05-05 13:12 (UTC) |
| Last Updated: | 2021-11-08 16:08 (UTC) |
Dependencies (2)
- udev (eudev-git, eudev, nldev, systemd-homed-containers, systemd-git, systemd-selinux, systemd)
- git (git-git, git-vfs, git-run-command-patch-git) (make)
Latest Comments
abouvier commented on 2022-03-08 05:43 (UTC) (edited on 2022-03-08 05:47 (UTC) by abouvier)
After investigation, it's the rule
SUBSYSTEM=="input", ENV{ID_INPUT_JOYSTICK}=="?*", TAG+="uaccess"in/usr/lib/udev/rules.d/70-uaccess.rulesthat gives access to all the inputs auto-detected as joystick.And
/usr/lib/udev/rules.d/70-joystick.rulesjust adds a property to the only two joysticks listed in/usr/lib/udev/hwdb.d/70-joystick.hwdb.fabiscafe commented on 2022-02-01 10:13 (UTC)
@abouvier There is a general rule-set /usr/lib/udev/rules.d/70-joystick.rules; /usr/lib/udev/hwdb.d/70-joystick.hwdb. That's why many devices work out of the box. In fact many of our rules are not necessary, because the devices would work just fine by themself. They are still available to complete the set if someone wants to ship no general rule, but device specific (game-devices-udev is not for Arch, but general purpose).
Yes, in best case it should end up in upstream systemd, but I sadly do not have time and money to test the devices and send MRs out.
abouvier commented on 2022-02-01 09:21 (UTC)
This means that you will have to add a rule for every gamepad in existence? Shouldn't these rules be added to upstream
udev?fabiscafe commented on 2022-02-01 08:50 (UTC)
@abouvier: udev rules can be granular and so a lot more secure. We go for uaccess to only allow the device being used while the user is logged in on users local PC. On top of that not everything is covered by the input group, as not everything is an input device. (mostly VR)
Please also see: https://wiki.archlinux.org/title/Users_and_groups#Pre-systemd_groups
abouvier commented on 2022-02-01 08:24 (UTC)
Why these rules are necessary? Add users in the
inputgroup is not sufficient? Or it's an alternative solution?