Linux: Chromium misremaps Xbox Series axes and triggers for virtual 045e:0b13 device

Open

#84 opened on Aug 15, 2026 0 comments 0 reactions 1 assignee View on GitHub

@LizardByte-bot is already working on this.

Since Aug 15, 2026.

Assessment

This issue has not been assessed yet.

Description

Environment

Host OS: Linux
Virtual controller provider: libvirtualhid through Sunshine
Profile: Xbox Series
Browser: Chromium
Reported identity: Sunshine (libvirtualhid) X-Box Series Controller (STANDARD GAMEPAD Vendor: 045e Product: 0b13)
Tester: https://app.lizardbyte.dev/gamepad-tester/

Observed behavior

Chromium applies the following incorrect routes:

LT controls right-stick X.
RT controls LT.
Right-stick Y controls RT.
Right-stick X controls right-stick Y.

The same controller works correctly in Steam's controller tester. Firefox does not show this axis/trigger routing failure.

Source-level explanation

The Linux uinput backend deliberately presents the Xbox Series profile as Bluetooth 045e:0b13, while emitting canonical Linux/XInput-style axes:

ABS_X, ABS_Y
ABS_RX, ABS_RY
ABS_Z, ABS_RZ

Chromium selects its physical Xbox Series Bluetooth mapper for 045e:0b13. That mapper expects the physical Bluetooth joydev ordering rather than the ordering produced by the virtual uinput device. The reported four misroutes correspond directly to that mismatch.

Chromium source:
https://chromium.googlesource.com/chromium/src/+/HEAD/device/gamepad/gamepad_standard_mappings_linux.cc

Expected behavior

Chromium should expose standard Gamepad API controls with:

LT and RT on buttons 6 and 7.
Right-stick X/Y on axes 2 and 3.
Share on button 17.

Constraints

Steam compatibility is the priority and currently works. Do not reorder the Linux backend's emitted axes merely to satisfy Chromium without proving Steam and Firefox remain correct. Evaluate a consumer-safe transport identity or an exact browser/tester normalization path. Keep Windows behavior unchanged.

Dominant language: C++
Stars: 57
Forks: 15
Avg merge: 11h 15m
Merged PRs (30d): 33

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues