qmk/qmk_firmware

[Bug] 50-qmk.rules udev rule breaks game controllers

Open

#24,222 opened on Jul 31, 2024

View on GitHub
 (13 comments) (0 reactions) (0 assignees)C (43,867 forks)batch import
bughelp wanted

Repository metrics

Stars
 (20,368 stars)
PR merge metrics
 (Avg merge 20d 9h) (27 merged PRs in 30d)

Description

Describe the Bug

When you install this file according to the docs, you end up with game controllers (non qmk based, regular game controllers) not working anymore.

I've seen this behaviour with xbox series bluetooth controllers and xpadneo driver.

Once you remove qmk udev rule and reload, controller works again.

It is noticeable as apps not being able to receive controller inputs. You press keys, move sticks, etc and there is no input in the apps. Hovewer, evtest still shows input data.

It doesn't matter if QMK keyboard (or any input device other than gamepad itself) is connected to the system.

Keyboard Used

irrelevant

Link to product page (if applicable)

also irrelevant

Operating System

Arch Linux

qmk doctor Output

not using qmk cli

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

none

Additional Context

No response

Contributor guide

Research direction
Investigate the udev rule file (50 qmk.rules) to identify which rule (likely SUBSYSTEM=="input" or others) is interfering with game controller input. Compare with standard udev rules for game controllers and test removing specific lines or modifying permissions.
Tech stack
c
Domain
devops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Linuxudev
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70