isXander
[Bug] detects keyboard as controller
Current Behaviour
On every boot, is asks me if I want to map my KBDFANS TIGER80 System Controller, even though the KBDFans Tiger 80 is a Keyboard.
Expected Behaviour
Not detect my Keyboard as a controller and ask if I want to map it on every boot
Screenshots
Reproduction Steps
Open minecraft with the keyboard attached
Logs
[14:01:20] [Render thread/INFO]: Initializing Controlify...
[14:01:20] [Render thread/INFO]: Loading Controlify config...
[14:01:20] [Render thread/INFO]: [SDLNativesLoader] Attempting to load SDL3 from SDL3
[14:01:20] [Render thread/INFO]: [LoadedSDLNatives] Loading SDL3 version: 3.2.12. Java bindings targeting: 3.2.16
[14:01:20] [Render thread/WARN]: [LoadedSDLNatives] SDL3 NATIVE LIBRARY VERSION MISMATCH! Java bindings are targeting a different version of SDL3 than the loaded native library. This may cause issues.
[14:01:21] [Render thread/INFO]: [LoadedSDLNatives] Successfully initialised SDL subsystems
[14:01:21] [Render thread/INFO]: [SDLNativesLoader] Successfully loaded SDL3 natives
[14:01:21] [Render thread/INFO]: Successfully loaded 362 gamepad mapping entries!
[14:01:21] [Render thread/INFO]: Using SDL to identify controller type.
[14:01:21] [Render thread/INFO]: [ControllerManager] [Controller #SDL-1] SDL GUID driver signature: Unknown
[14:01:21] [Render thread/INFO]: [ControllerManager] Controller connected: 'KBDFANS TIGER80 System Control'#SDL-1-HID[VID=0x4b42, PID=0x0011] (null)
[14:01:21] [Render thread/INFO]: Steam Deck state: NOT_STEAM_DECK
[14:01:21] [Render thread/INFO]: Using SDL to identify controller type.
[14:01:21] [Render thread/WARN]: [ControllerManager] [Controller #SDL-1] Tried to create controller that already is initialised: SDL-1.
Mod Version
2.2.1+1.21.5-fabric
Controller
No response
Bluetooth
- [ ] Yes
Operating System
Linux/SteamOS
ARM
- [ ] Yes
Additional Information
No response
Just to make sure...
- [x] I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
- [x] I have made sure there are no other issues describing the same problem on the issue tracker.
I think this is an issue with Linux. For me the keyboard only shows up as a controller when using the app image version of Prism Launcher (or whatever launcher you are using). I would try switching to the flatpack version and see if that solves the issue.
If not, (or you were already using a flatpack launcher) then you could see if Linux is picking up your keyboard as a controller in the Settings app. On kde, look for a tab labeled "Game Controllers". If it there, then you can apply a blacklist for that device. That is out of the scope of my knowledge, so I would google how to do that.
Hope this helps!
I will try next week whe nI will be back from vacations, thanks! (I am using a native version from the fedora copr)