Please describe your issue in as much detail as possible:
I've been using my GuliKit KK3 controller with Steam on Linux without issue for over a year. The controller presents itself as a generic Xbox controller, so everything worked fine. As of this past week, the mappings are suddenly all wrong, and some buttons are simply not detected.
The 'Y' button is mapped to 'X' instead, left bumper is mapped to 'Y', and the view/menu buttons are mapped to the bumpers. The 'X' button isn't detected at all, and neither are the joystick buttons, the right bumper, or the share/capture buttons. This happens even when trying to remap the buttons using the "Setup Device Inputs" option in the Controller Layout dialog.
All of the problems are happening exclusively within Steam and affect all Steam games, even with Steam Input turned off. Applications other than Steam still see the controller just fine.
Steps for reproducing this issue:
Install and launch latest Steam from Flathub on Fedora Silverblue 43
Connect Xinput-compatible controller via Bluetooth
Go to Steam settings > Controller
Disable Steam Input and select "Begin Test" for the connected controller
Update: This might be a kernel Bluetooth regression. Noticing broken behavior outside of Steam now, and the controller does seem to be mapped correctly when plugged in via USB. Will need to investigate further...
Your system information
Please describe your issue in as much detail as possible:
I've been using my GuliKit KK3 controller with Steam on Linux without issue for over a year. The controller presents itself as a generic Xbox controller, so everything worked fine. As of this past week, the mappings are suddenly all wrong, and some buttons are simply not detected.
The 'Y' button is mapped to 'X' instead, left bumper is mapped to 'Y', and the view/menu buttons are mapped to the bumpers. The 'X' button isn't detected at all, and neither are the joystick buttons, the right bumper, or the share/capture buttons. This happens even when trying to remap the buttons using the "Setup Device Inputs" option in the Controller Layout dialog.
All of the problems are happening exclusively within Steam and affect all Steam games, even with Steam Input turned off. Applications other than Steam still see the controller just fine.
Steps for reproducing this issue: