Attaching USB gamepad device to qube does not work
Qubes OS release
4.2.3, 4.2.4, 4.3.0-rc1
Brief summary
Attaching USB gamepad (Xbox One S) to qube (gaming qube Debian 12 HVM with GPU passthrough, USB qube Debian 12 Minimal) does not work.
Attaching other USB devices (like a USB mouse) does work.
Steps to reproduce
- Plug gamepad into PC using USB cable
- Try to attach USB gamepad to gaming qube using
qvm-usb attach gaming sys-usb:id - :(
Expected behavior
Gamepad is successfuly attached to qube.
Actual behavior
Gamepad is not attached to qube, as seen from lsusb output inside qube. No games or software detect it.
Additional information
Attaching the gammepad through the gui (tray) breaks the tray, it shows the device as "attached" (qvm-usb does not) but detaching it is impossible ("device not attached to qube gaming"). Attaching it with the --persistent flag also did not work (though in that case qvm-usb in dom shows it as attached).
Probably related: #9562
Update: I have no idea what component got updated, but the issue is gone. Closing as fixed.
Sorry for closing and re-opening, but it seems that the issue is actually not fixed. It just worked with a different brand of controller (GuliKit), so I assumed it'd also work with the Xbox One S controller, but alas, it does not.
More testing:
What works:
- Gulikit KK3 Max Bluetooth (Initial connection is finnicky, but it works decently well afterwards)
- Gulikit KK3 Max Wired (Badly, this mode does not like Linux in general)
- Xbox One S Bluetooth
- Gulikit ES Pro Bluetooth (very well)
- Gulikit ES Pro Wired (very well)
What does not work:
- Xbox One S Wired (I do not know why)
- Gulikit KK 3 Max 2.4GHz Dongle (probably a Qubes issue)*
* The GK KK3 Max's wireless dongle identity changes depending on whether a controller is connected to it or not. This means that attaching the dongle works, but it disconnects from a VM immediately after connecting a controller to it. Auto-attaching (r4.3) also does not work.