Hi, due to an udev patch [1] some joysticks don't get recognized as joysticks anymore (e.g. Saitek PLC Pro Flight Rudder Pedals) as they don't match udevs minimum "requirements" for joysticks. This results in a not "out-of-the-box"-usable joystick as an additional permission of the joystick dev (e.g. /dev/input/js0) is not getting set and thus the user is unable to use the device. To workaround this issue, I added following udev rule in "/etc/udev/rules.d/70-joysticks.rules" which sets ID_INPUT_JOYSTICK to 1 and thus udev is handling this device as joystick again: KERNEL=="*", ATTRS{idVendor}=="06a3", ATTRS{idProduct}=="0763", ENV{ID_INPUT_JOYSTICK}="1" As this can only be done for every single product which is misinterpreted as keyboard instead joystick, I suggest to put an additional udev rule in the udev package. Content of this rule would be the line above and additional lines like the one above for other products. Where does this file needs to go? Should it go into /etc/udev/rules.d or should the udev package install a custom udev rule into another place like /usr/lib/udev/rules.d/? Thanks and regards Daniel [1] https://github.com/systemd/systemd/commit/bc85f8b51d962597360e982811e674c126850f56
opened upstream issue https://github.com/systemd/systemd/issues/34642
I don't think it makes sense for us to ship custom udev rules for this. Please address the issue upstream.
