Microsoft wireless keyboard/mouse transceiver being recognized as a gamepad

[fscherrer]

(GNU/Linux)
I have a Microsoft wireless keyboard and mouse which uses a wireless transceiver:

scherrer@home ~ $ lsusb | grep -i microsoft
Bus 003 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth

and it's beeing recognized as a gamepad (this is printed during the game startup):

Controller 0, Microsoft Microsoft® 2.4GHz Transceiver v8.0, will use generic MonoGameJoystick support.

It happens with other MonoGame games, but manageable removing the ~/.config/MonoGame/MonoGameJoystick.cfg file.
Sadly, this workaround isn't working with Rogue Legacy.
If I remove this file it gets recreated when I start the game, and so, if I try to play, the character start moving to the left by itself.
I've tried with a Null Configuration[pcgamingwiki.com] and it worked partially: the character isn't moving to the left by itself and I can use the keyboard, but the game still wants that I press "Y", "A" and so on, which is really anoying.


Is there any tweek I can try?

(edit: typo)

[fscherrer]

Why does this forum have a Technical Support subtopic if no devs responds a topic in more than 3 months?

[fscherrer]

With the help of the guys from SpikySnail, developers of Super Splatters*, I got to the SDL and then to udev.
evtest reports 3 entries for "Microsoft Microsoft® 2.4GHz Transceiver v8.0":

# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Power Button
/dev/input/event1:      Power Button
/dev/input/event2:      Microsoft Microsoft® 2.4GHz Transceiver v8.0
/dev/input/event3:      Microsoft Microsoft® 2.4GHz Transceiver v8.0
/dev/input/event4:      Microsoft Microsoft® 2.4GHz Transceiver v8.0
/dev/input/event5:      Sony Computer Entertainment Wireless Stereo Headset

event2 is the keyborad.
event3 is the mouse.
event4 is the joystick (wrong, I never had one)

udevadm:

 # udevadm info --query=all --name=input/event4
P: /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.2/input/input14/event4
N: input/event4
S: input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v8.0-if02-event-joystick
S: input/by-path/pci-0000:00:12.1-usb-0:2:1.2-event-joystick
E: DEVLINKS=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v8.0-if02-event-joystick /dev/input/by-path/pci-0000:00:12.1-usb-0:2:1.2-event-joystick
E: DEVNAME=/dev/input/event4
E: DEVPATH=/devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.2/input/input14/event4
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_JOYSTICK=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_MODEL=Microsoft®_2.4GHz_Transceiver_v8.0
E: ID_MODEL_ENC=Microsoft®\x202.4GHz\x20Transceiver\x20v8.0
E: ID_MODEL_ID=0745
E: ID_PATH=pci-0000:00:12.1-usb-0:2:1.2
E: ID_PATH_TAG=pci-0000_00_12_1-usb-0_2_1_2
E: ID_REVISION=0656
E: ID_SERIAL=Microsoft_Microsoft®_2.4GHz_Transceiver_v8.0
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030101:030102:030000:
E: ID_USB_INTERFACE_NUM=02
E: ID_VENDOR=Microsoft
E: ID_VENDOR_ENC=Microsoft
E: ID_VENDOR_ID=045e
E: MAJOR=13
E: MINOR=68
E: SUBSYSTEM=input
E: TAGS=:udev-acl:
E: USEC_INITIALIZED=441608451

The easiest way to workaround this issue was to remove group permissions:

# chmod g-rwx /dev/input/event4

And now I can play Rogue Legacy, Bleed and probably other games :)

*I was having problems with Super Splatters too, but, after contacting them, they responded really quick and, in less than a week, they provided a fix. (I said them it was a problem with my setup, 'cause it happened with other games, but even so they did a fix)

[Cappellaio Matto]

Thank you very much for sharing your solution. I was having this very same issue with Metro Last Night and Transistor on Fedora 20/22. Changing the group permission worked!

[terrem88]

thanks.
that was a very good idea.

sad that devs doesn`t look here much.

[Marlock]

Various Microsoft Keyboards, Mouses and Wireless Nano Receivers for them are misidentified on Linux yet.

It's a mistake on their part, making hardware that presents itself somewhat wrong to the system.

A handful of other brands and models have similar issues.

Follow this link, the instructions there are probably going to fix your issue, teaching linux the brands and models it has to give a "special treatment", killing the fake joystick as soon as it's created:

https://github.com/denilsonsa/udev-joystick-blacklist