Several keyboard devices are erroneously tagged with ID_INPUT_JOYSTICK because of random buttons they set. For example, the LiteOn Lenovo Calliope USB Keyboard sets BTN_TRIGGER, BTN_TOP2, BTN_PINKIE and BTN_BASE, see libinput issue 745 for details. ID_INPUT_JOYSTICK triggers the uaccess rules, making those keyboards easily accessible. That's not a problem in the LiteOn example since that event node doesn't contain the normal keys and eavesdropping on volume keys is probably not very interesting. Improve the joystick detection by adding heuristics similar to what libinput 1.20 uses: check for some specific set of keys that are common on keyboards but very unlikely on joysticks. If enough of those are present (or the device has less than 2 axes or joysticks), don't tag it as joystick. libinput also checks for > 10 keyboard keys, but this is not done here to be more conservative.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
