Skip to content

Xemu fails to detect remote gamepad #200

@zslliu

Description

@zslliu


Describe the bug

The Xemu emulator, when running inside a Lutris container, fails to detect a connected gamepad (Switch Pro Controller). The controller is recognized by other applications and emulators (Wine, PCSX3, Yuzu) within the same container, but not by Xemu. The issue occurs when the controller is connected to a client machine accessing the Lutris host over the local network via a browser.

Steps to reproduce the behavior:

  1. Connect a Switch Pro Controller to a client computer.
  2. On the client computer, open a web browser and connect to the Lutris host machine on the local network.
  3. Launch the Xemu emulator from within the Lutris interface.
  4. Attempt to configure or use the controller in Xemu's input settings.
  5. Observe that the controller is not detected by Xemu.
    
    Expected behavior
    
    Xemu, when running within the Lutris container, should detect and allow the use of the Switch Pro Controller that is connected to the remote client, consistent with the behavior of other emulators like PCSX3 and Yuzu in the same environment.
    
    Screenshots
Image
  • Host OS Version: Ubuntu 24.04
  • Browser Version: [Chrome 139.0.7258.139]
  • Controller Model: Nintendo Switch Pro Controller
    
    Additional context
    
  • The fix from commit Joystick Interposer evdev support, fixes SDL, Wine, Retroarch, RPCS3, and more. #173 has been applied.
  • The controller works as expected in Wine, PCSX3, and Yuzu within the same new container.
  • The issue has been tested and confirmed with both Xemu v0.7.111 and the latest version, v0.8.96.
  • The controller is detected correctly by Xemu if it is physically plugged into the host machine. The problem only occurs when the controller is connected to a remote client accessing the host via a browser.
  • I confirm that this issue is relevant to the scope of this project. If you know that upstream projects are the cause of this problem, please raise the issue there.
  • I confirm that I have read other open and closed issues and that duplicates do not exist.
  • I confirm that the issue is easily reproducible and explained thoroughly.
  • I confirm that relevant log files have been included as explained below. Any relevant additional log files have also been included.
  • I confirm that no portion of this issue contains credentials or other private information, and it is my own responsibility to protect my privacy.
  • I confirm that the authors of this issue does not willfully breach or infringe legal regulations, in any and all global law, regarding trademarks, trade names, logos, patents, or any and all other forms of external intellectual property, as well as adhering to software license terms of open-source and proprietary software projects.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions