protonscr

Steam Crashes when Rumble Pad 2 is plugged in

steamopen Steam clientDistro Family: DebianGeneral controller / Steam Input
ValveSoftware/steam-for-linux#12367 · opened 2025-10-08 by jordanlikescurry · updated 2025-10-21 · 2 comments · github
Jjordanlikescurry 2025-10-08 github

Your system information

  • Steam client version (build number or date): 1759461205
  • Distribution (e.g. Ubuntu): Debian 13 Trixie
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: [generate by running this command in a termina

steam-logs.tar.gz

  • GPU: AMD

Please describe your issue in as much detail as possible:

I have my rumble pad 2 plugged in. When I launch steam it crashes on the "loading user settings" portion of the launch process. I have tested this with another account and even with the controller plugged in the crash does not happen. Recently I disabled steam input on Hades 2 as the game recommended it.

Steps for reproducing this issue:

  1. Install steam (either through flatpak or the official steam .deb or through the debian steam-installer repo package)
  2. Launch steam with controller plugged in
  3. Steam launches as normal
  4. Close steam by going to steam > Exit.
  5. Launch steam again with controller stilled plugged in
  6. Steam crashes
  7. (GOTO 5)
  8. Unplug rumble pad 2
  9. Launch steam again but without the rumble pad 2 plugged in
  10. This time steam launches normally 🤌

Steps 8-10 were only tested on 1759461205 installed through the debian steam-installer package.
Steps 1-6 were tested on the other package versions (flatpak and official .deb)

MmaunzCache 2025-10-16 github

I may or may not have a similar/related issue.
Could you try the following:

  1. Launch steam
  2. Plug in controller
  3. Start any game that uses at least Proton 9

If that would lead to a crash for you, that is a bonus and I would join the party with more details.

In general you might want to look into the logs e.g. via

# Show logs for current boot
journalctl -b 0
# or
sudo dmesg | grep usb | less

And check if at the very end you can find errors related to usb e.g. error code -32 or -71
If so - check also for your initial error guide - this might help debug this.

Jjordanlikescurry 2025-10-21 github

All right I kind of ignored this issue because I bought a new controller and it resolved my issue.

I did go back and try it with my rumble pad 2 though. I did notice that steam crashes immediately after I plug in the controller.

Here's the output of dmesg after I plugged in my controller.

[14427.696609] usb 1-4: new low-speed USB device number 17 using xhci_hcd
[14427.947405] usb 1-4: New USB device found, idVendor=046d, idProduct=c218, bcdDevice= 1.00
[14427.947411] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[14427.947413] usb 1-4: Product: Logitech RumblePad 2 USB
[14427.947415] usb 1-4: Manufacturer: Logitech
[14427.992148] input: Logitech Logitech RumblePad 2 USB as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-4/1-4:1.0/0003:046D:C218.000B/input/input36
[14427.992318] logitech 0003:046D:C218.000B: input,hidraw6: USB HID v1.10 Joystick [Logitech Logitech RumblePad 2 USB] on usb-0000:02:00.0-4/input0
[14427.992328] logitech 0003:046D:C218.000B: Force feedback for Logitech variant 2 rumble devices by Anssi Hannula [email protected]
[14428.989176] input: Microsoft X-Box 360 pad 1 as /devices/virtual/input/input37
[14429.425581] IPC:CSteamEngin[18426]: segfault at 0 ip 00000000f3bc51a8 sp 00000000d60fbe50 error 4 in libvstdlib_s.so[a81a8,f3b6d000+b2000] likely on CPU 3 (core 3, socket 0)
[14429.425592] Code: ff 50 68 6f 03 00 00 52 89 54 24 1c e8 31 87 fa ff 83 c4 10 84 c0 75 c0 cc 85 ed 8b 54 24 0c 74 6f 8d 04 3e 8d b6 00 00 00 00 <0f> b6 55 00 83 c5 01 83 c6 01 88 56 ff 84 d2 75 17 89 f0 c6 40 ff

This controller still functions just fine as a controller however; using heroic launcher and this controller is just fine. So I think this still classifies as a bug in steam.

Nothing extracted yet.