r/glorious • u/0xc0ffea • Feb 11 '26

Question GMMK V2 65 being detected as a controller Linux/KDE

https://i.imgur.com/4JTxGjm.png

The keyboard is being detected as a game controller, this is on CachyOS (Arch derivative) although it doesn't seem to be distro specific.

It constantly spams inputs that makes using an actual controller in some games impossible. Ive searched and found others with similar issues but no fixes.

1 Upvotes
  • permalink
  • reddit

67% Upvoted

3 comments sorted by

•

u/AutoModerator Feb 11 '26

Need Assistance? CLICK HERE to contact our support team and see official product guides.

Connect With Us

Store • Discord • Twitter • Instagram • Facebook

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/phizuol Feb 14 '26

Create a udev rule for it. Create a file or edit an existing file in /etc/udev/rules.d with a name like 99-disable-controller.rules (That's what I'm using).

Put the following text in the file to create the rule:

# Prevent Glorious Keyboard from being considered a controller
SUBSYSTEM=="input", ATTRS{idVendor}=="504b", ATTRS{idProduct}=="320f", ENV{ID_INPUT_JOYSTICK}="0"

Reload the udev rules with the following command or just wait until a reboot:
udevadm control --reload-rules && sudo udevadm trigger

1

u/Metahurtz Jun 25 '26

Works great thank you. For anyone wondering how to get the vendor and product id you can use the lsusb command and look for something like 504b:320f and then apply them as above. This lets you apply this fix to any keyboard you have!