We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3239

Summary: SDL2 does not detect joysticks with fewer than 2 axes
Product: SDL Reporter: Rena Kunisaki <hyperhacker+sdlbugs>
Component: joystickAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: minor    
Priority: P2    
Version: 2.0.4   
Hardware: x86_64   
OS: Linux   

Description Rena Kunisaki 2016-01-13 09:26:40 UTC 
On Arch Linux, using the sdl2-jstest program (version 0.2.0), joysticks with fewer than 2 axes aren't detected.

I've been developing the client-side code for a microcontroller to behave as a USB joystick. Everything works fine, until I alter the report descriptor to specify fewer than 2 axes. After that, `sdl2-jstest -l` reports no joysticks found. `jstest /dev/input/js0` works regardless and shows the joystick's status correctly.
Comment 1 Sam Lantinga 2017-08-12 20:08:02 UTC 
2 axes was chosen as the minimum to be useful for controlling games, and to filter out things like mice that have a scrollwheel that mis-identify as joysticks.

Do you have an application that only needs 1-axis control?
Comment 2 Ryan C. Gordon 2018-08-06 21:20:18 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.