[Bug 60226] New: Wine XInput: XInputGetState returns 0 buttons for connected Bluetooth Xbox One controller

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=60226

            Bug ID: 60226
           Summary: Wine XInput: XInputGetState returns 0 buttons for
                    connected Bluetooth Xbox One controller
           Product: Wine
           Version: 11.13
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: xinput
          Assignee: [e-mail]
          Reporter: [e-mail]
  Target Milestone: ---
      Distribution: ---

Created attachment 81926
  --> http://bugs.winehq.org/attachment.cgi?id=81926
Complete Wine XInput probe output and stderr (wine-staging 11.13) plus evdev
monitor capture of the connected Bluetooth Xbox One controller

On a clean Wine prefix (default layout, no DLL overrides, no third-party DLLs),
a
standalone Windows XInput probe polling XInputGetState(0) reports the
controller as
CONNECTED (result == ERROR_SUCCESS) but the button/trigger/thumb-stick state is
permanently zero — buttons=0x0000, rt=0, lt=0, lx=0, ly=0 — even while the
physical
buttons and D-pad are pressed. The kernel-level input IS delivered to the
controller's
evdev node (a monitor captures button/axis events), so the break is in Wine's
XInput
backend: it enumerates the controller but never maps incoming HID/evdev input
into the
XINPUT_STATE it returns.

Environment:
- Nobara Linux 44 (KDE Plasma), x86_64
- Kernel: 7.1.4-200.nobara.fc44.x86_64
- Wine: 11.13 (Staging), package wine-staging-11.13-1.x86_64
- Controller: Microsoft Xbox Wireless Controller (Bluetooth), VID 045e PID
0b13, fw 0522
- Driver: xpadneo (hid-xpadneo)

Repro:
1. Connect an Xbox One Wireless Controller over Bluetooth (xpadneo).
2. Create a clean prefix: WINEPREFIX=/tmp/wine-clean wineboot -i
3. Run a minimal XInput probe (loop XInputGetState(0) ~800x over 8s) under it
while
   pressing A / D-pad.
4. Observed: t=0 result=0 packet=1 buttons=0x0000, then done — no button
changes ever.

Expected: XInputGetState(0) returns the pressed button bits when physical
buttons are
pressed, matching Windows.

Actual: returns result=0 (connected) but buttons=0x0000 permanently, while the
same
presses produce valid events at the kernel evdev layer.

Attached: complete probe output + wine stderr + evdev monitor capture.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.