Connecting Steam Controller Crashes Steam

steamopen Steam clientSteam controllerDistro Family: Fedora

ValveSoftware/steam-for-linux#13195 · opened 2026-05-13 by somone77 · updated 2026-08-27 · 15 comments · github

Ssomone77 2026-05-13 github

Your system information

Steam client version (build number or date): 1778281814 (flatpak)
Distribution (e.g. Ubuntu): Fedora 44
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
GPU: Intel(R) HD Graphics 620 (KBL GT2)

Please describe your issue in as much detail as possible:

Steam crashes with segfault, CSteamController crashes with segfault

dmesg:

[ 1384.635285] usb 1-3: new full-speed USB device number 6 using xhci_hcd
[ 1384.760904] usb 1-3: New USB device found, idVendor=28de, idProduct=1302, bcdDevice= 3.07
[ 1384.760930] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1384.760941] usb 1-3: Product: Steam Controller
[ 1384.760951] usb 1-3: Manufacturer: Valve Software
[ 1384.760959] usb 1-3: SerialNumber: FXA996100073F
[ 1384.770520] input: Valve Software Steam Controller Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:28DE:1302.0005/input/input21
[ 1384.771461] input: Valve Software Steam Controller Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:28DE:1302.0005/input/input22
[ 1384.822845] hid-generic 0003:28DE:1302.0005: input,hiddev96,hidraw0: USB HID v1.11 Mouse [Valve Software Steam Controller] on usb-0000:00:14.0-3/input0
[ 1386.324215] input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input24
[ 1387.544767] CSteamControlle[8929]: segfault at 0 ip 0000000000000000 sp 00000000da9655dc error 14 likely on CPU 1 (core 1, socket 0)
[ 1387.544779] Code: Unable to access opcode bytes at 0xffffffffffffffd6.

systemd-coredump can vary

May 12 16:52:17 fedora-htpc kernel: CSteamControlle[8929]: segfault at 0 ip 0000000000000000 sp 00000000da9655dc error 14 likely on CPU 1 (core 1, socket 0)
May 12 16:52:17 fedora-htpc kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
May 12 16:52:17 fedora-htpc systemd-coredump[9708]: Process 8865 (steam) of user 1000 terminated abnormally with signal 11/SEGV, processing...
May 12 16:52:17 fedora-htpc steam[8768]: crash_20260512165216_35.dmp[500]: Finished uploading minidump (out-of-process): success = yes
May 12 16:52:17 fedora-htpc steam[8768]: crash_20260512165216_35.dmp[500]: response: CrashID=bp-84351c0a-d42d-4f72-b97a-018822260512
May 12 16:52:17 fedora-htpc steam[8768]: crash_20260512165216_35.dmp[500]: file ''/tmp/dumps/crash_20260512165216_35.dmp'', upload yes: ''CrashID=bp-84351c0a-d42d-4f72-b97a-018822260512''
May 12 16:52:20 fedora-htpc systemd-coredump[9709]: [🡕] Process 8865 (steam) of user 1000 dumped core.
                                                    
                                                    Stack trace of thread 159:
                                                    #0  0x0000000000000000 n/a (n/a + 0x0)
                                                    #1  0x00000000f37d36ae _ZN16SteamThreadTools7CThread22ThreadExceptionWrapperEPv (libtier0_s.so + 0x336ae)
                                                    #2  0x00000000f37d0e0e n/a (libtier0_s.so + 0x30e0e)
                                                    #3  0x00000000f37d16d0 CatchAndWriteMiniDumpExForVoidPtrFn (libtier0_s.so + 0x316d0)
                                                    #4  0x00000000f37d1718 CatchAndWriteMiniDumpForVoidPtrFn (libtier0_s.so + 0x31718)
                                                    #5  0x00000000f37d67e2 _ZN16SteamThreadTools7CThread10ThreadProcEPv (libtier0_s.so + 0x367e2)
                                                    #6  0x00000000f79d5c8a n/a (/app/lib/i386-linux-gnu/libc.so.6 + 0x98c8a)
                                                    ELF object binary architecture: Intel 80386

I originally attempted on the Steam install from rpmfusion-nonfree, I attempted to delete ~/.steam and ~/.local/share/Steam, I uninstalled the RPM version and installed the flatpak from flathub and experienced the same behavior.

I'm attempting this with the controller plugged in directly.

The controller has not successfully updated with the latest firmware (due to the crashes), so its firmware it shipped with is what's on it.

When Steam is not running, the controller acts as a standard input and the trackpads can be used and buttons for mouse control.

Steps for reproducing this issue:

Start Steam
Connect Steam Controller
After short delay, segfault occurs and Steam crashes

steam-logs.tar.gz

Kkisak-valve maintainer 2026-05-13 github

Hello @somone77, this reads like the issue being tracked at #13186. Closing in favor of the older issue report.

Ssomone77 2026-05-13 github

@kisak-valve Are you sure? Both #13186 and #13193 state their crash occurs when launching a game. This is crash of Steam itself before any action is taken.

The author of #13186 also indicates that it may be an incompatibility with xpad which is not present on my system.

root@fedora-htpc:~# lsmod | grep xpad
root@fedora-htpc:~#

Ssomone77 2026-05-13 github

I verified the steam hardware udev rules are installed via the steam-devices package

# dnf list --installed | grep steam-devices
steam-devices.noarch                                 1.0.0.101^git20260123.e0ab314-7.fc44 fedora

This is slightly older than the master branch of https://github.com/ValveSoftware/steam-devices
I manually updated the udev rules with the latest from the master branch.
No change in behavior.

Ssomone77 2026-05-13 github

I found https://github.com/ValveSoftware/steam-for-linux/issues/4127 and this got me thinking.

Located in my browser history
https://old.reddit.com/r/gnome/comments/1dq9tel/i_get_this_prompt_every_time_i_plug_in_my_steam/lamovn9/

Sure enough, I had over a year ago disabled the XTest extension in dconf.

I removed that dconf setting and my crashes have stopped.

So it seems XTest being disabled causes a segfault in this configuration. This reiterates #10181 however, which doesn't seem to have been addressed?

TTheGrol 2026-05-13 github

Hello!

I had the same issue on my desktop with a switch pro controller plugged into steam.
Steam would crash trying to open overwatch while it was plugged in. strangely, I have no issue when my PS4 controller is plugged in though.

I am on Fedora 44, Have an AMD RX 7800 XT, and have an AMD Ryzen 7 7700x
I am using the RPMFusion Package, and not flatpak.

If you need any more info, let me know. Here's what I pulled the first time it crashed:

src/tier1/KeyValues.cpp (3120) : Assertion Failed: Error while parsing text KeyValues for resource controller_mappings
src/tier1/KeyValues.cpp (3120) : Assertion Failed: Error while parsing text KeyValues for resource controller_mappings
assert_20260512222346_40.dmp[41220]: Uploading dump (out-of-process)
/tmp/dumps/assert_20260512222346_40.dmp
src/tier1/KeyValues.cpp (3120) : Assertion Failed: Error while parsing text KeyValues for resource controller_mappings
src/tier1/KeyValues.cpp (3120) : Assertion Failed: Error while parsing text KeyValues for resource controller_mappings
src/steamUI/controllerconfig.cpp (720) : No config for controller found locally, no config loaded as of now
src/steamUI/controllerconfig.h (126) : Assertion Failed: CPrepareConfigWorker failed for AppID 2357570
src/clientdll/steamengine.cpp (2838) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled

Aadamdjensen 2026-05-13 github

Is this potentially related to/dupe of #13117 ?

RRLB2310 2026-05-14 github

Referenced in "Steam Client Beta - May 13th"

Fixed a crash related to the Steam Controller on Linux

Possibly fixed. Needs retest

Ppsychoelfx 2026-05-15 github

Tried the beta. Still crashing as soon as connected.

Ssomone77 2026-05-15 github

I retested on client version 1778803745
No change in behavior.

However I'll reiterate that I know my issue, specifically, is the lack of Xtest which I had disabled due to the infuriating "Remote Control" prompts. Ref: #10442 #9209

I don't know how you'd like to handle this report. If Valve's position is that the controller requires Xtest, then perhaps the problem is not handling the failure gracefully. But given this has been the case for years, I don't believe there will be movement in that area.

So this issue is "Steam crashes when connecting a Steam Controller when using Gnome with Wayland and Xtest disabled"

Kkapple19 2026-05-19 github

Just throwing in my 2 cents that I am having a very similar/the same experience.

I am running Bazzite (Gnome) on a Framework Desktop.

Steam runs fine with no controllers connected, as far as I have seen.

Upon any of the following controllers connecting to my PC, Steam crashes:

L-Tek Dance Pad (Wired).
Playstation 5 Controller (Bluetooth).
Steam Controller (2026 (dumb that we have to make this clarification)) (Puck).

FWIW, I have a dongle-connected wireless keyboard that Steam seems to work fine with.

Running steam in a terminal reveals a segmentation fault, along with some complaints that The XTest extension doesn't exist.

I have also run the following command due to having repeated popups requesting Remote Desktop enable-ment:

gsettings set org.gnome.mutter.wayland xwayland-disable-extension '["Xtest"]'

which stopped the popups. The popups would trigger after starting the ITGmania application.

Let me know if any information I can provide from my end would help this issue.

For now, here's what steam outputs in a terminal after connecting my PS5 controller.

src/clientdll/inputgenerator_linux.cpp (347) : The XTest extension doesn't exist
src/clientdll/inputgenerator_linux.cpp (347) : The XTest extension doesn't exist
assert_20260519220705_48.dmp[35329]: Uploading dump (out-of-process)
/tmp/dumps/assert_20260519220705_48.dmp
crash_20260519220705_49.dmp[35332]: Uploading dump (out-of-process)
/tmp/dumps/crash_20260519220705_49.dmp
assert_20260519220705_48.dmp[35329]: Finished uploading minidump (out-of-process): success = no
assert_20260519220705_48.dmp[35329]: error: Peer certificate cannot be authenticated with given CA certificates
assert_20260519220705_48.dmp[35329]: file ''/tmp/dumps/assert_20260519220705_48.dmp'', upload no: ''Peer certificate cannot be authenticated with given CA certificates''
crash_20260519220705_49.dmp[35332]: Finished uploading minidump (out-of-process): success = no
crash_20260519220705_49.dmp[35332]: error: Peer certificate cannot be authenticated with given CA certificates
crash_20260519220705_49.dmp[35332]: file ''/tmp/dumps/crash_20260519220705_49.dmp'', upload no: ''Peer certificate cannot be authenticated with given CA certificates''
/var/home/kapple/.local/share/Steam/steam.sh: line 966: 34080 Segmentation fault         (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"

Ppsychoelfx 2026-05-19 github

I tried what another person tried and reinstalled Fedora with 44. Now it works just fine....🤷🏼‍♂️

Wwbwqq 2026-06-10 github

I am seeing a very similar crash with the Steam Controller 2026 on Fedora Linux.

Summary

Steam crashes when the Steam Controller 2026 / Steam Controller Puck is powered on while Steam is already running. If it doesn't crash straight away, as soon as a game is launched is crashes the game, sometimes the whole system.

Wireless itself seems to works. If I power on the controller first and then start Steam, everything seems to work and there are no crashes. The crash seems to happen when Steam has to handle the controller/puck appearing while Steam is already open, or sometimes when launching a game after the controller is connected.

The most recent firmware attempt did not solve it: Steam reported “update complete” instantly, but the logs afterwards still show repeated Steam controller device closed after HID IO failure.

System

OS: Fedora Linux 43
GPU: AMD
Steam client: current / recently updated
Controller: Steam Controller 2026
Connection: Steam Controller Puck
Puck USB ID: 28de:1304

Relevant Fedora packages are installed:

hidapi-0.15.0-2.fc43.x86_64
hidapi-devel-0.15.0-2.fc43.x86_64
steam-devices-1.0.0.101^git20260123.39e7bd0-8.fc43.noarch

Reproduction

This works:

1. Steam is closed.
2. Steam Controller Puck is plugged into USB.
3. Steam Controller is powered on and connects to the puck.
4. Steam is started afterwards
5. Controller works.

This crashes:

1. Steam is already running.
2. Steam Controller is powered on.
3. Controller connects / Steam detects the puck.
4. Steam crashes.

It sometimes crashes when launching a game after the controller is connected (if the controller is turned on after Steam has already been launched). Alternatively if Steam doesn't crash, then games almost always crash when launched in this situation.

Firmware updater behavior

I tried re-updating the firmware manually, which seems to do nothing. In dev mode (steam -dev). The updater says “update complete,” but it is suspiciously instantaneous. After that, the crash/problem persists, and the logs still show repeated HID IO failures.

So this does not seem to be fixed by simply running the firmware updater.

Relevant log excerpts

After running the firmware updater, Steam still detects the puck as multiple HID interfaces:

~/.steam/steam/logs/console_log.txt:
[2026-06-10 02:59:50] Added HIDAPI device 'Valve Software Steam Controller Puck' VID 0x28de, PID 0x1304, bluetooth 0, version 2, serial REDACTED, interface 2, usage page 0xff00, usage 0x0001, path = /dev/hidraw3, driver = NONE (DISABLED)
[2026-06-10 02:59:50] Added HIDAPI device 'Valve Software Steam Controller Puck' VID 0x28de, PID 0x1304, bluetooth 0, version 2, serial REDACTED, interface 3, usage page 0xff00, usage 0x0001, path = /dev/hidraw4, driver = NONE (DISABLED)
[2026-06-10 02:59:50] Added HIDAPI device 'Valve Software Steam Controller Puck' VID 0x28de, PID 0x1304, bluetooth 0, version 2, serial REDACTED, interface 4, usage page 0xff00, usage 0x0001, path = /dev/hidraw5, driver = NONE (DISABLED)
[2026-06-10 02:59:50] Added HIDAPI device 'Valve Software Steam Controller Puck' VID 0x28de, PID 0x1304, bluetooth 0, version 2, serial REDACTED, interface 5, usage page 0xff00, usage 0x0001, path = /dev/hidraw6, driver = NONE (DISABLED)
[2026-06-10 02:59:50] Added HIDAPI device 'Valve Software Steam Controller Puck' VID 0x28de, PID 0x1304, bluetooth 0, version 2, serial REDACTED, interface 6, usage page 0xff00, usage 0x0002, path = /dev/hidraw7, driver = NONE (DISABLED)

After that, Steam reports the puck firmware as a real version:

[2026-06-10 02:59:51]   Product:      Steam Controller Puck
[2026-06-10 02:59:51]   Product:      Steam Controller Puck
[2026-06-10 02:59:51]   Product:      Steam Controller Puck
[2026-06-10 02:59:51]   Product:      Steam Controller Puck
[2026-06-10 02:59:51]   Product:      Steam Controller Puck
[2026-06-10 02:59:51]   Firmware Version: 1780011095

But after the firmware updater says “update complete,” Steam still logs repeated HID IO failures:

[2026-06-10 03:00:12] Steam controller device closed after HID IO failure
[2026-06-10 03:00:12]   Product:      Steam Controller Puck
[2026-06-10 03:00:12]   Firmware Version: 1780011095

[2026-06-10 03:00:32] Steam controller device closed after HID IO failure
[2026-06-10 03:00:32]   Product:      Steam Controller Puck

[2026-06-10 03:00:52] Steam controller device closed after HID IO failure
[2026-06-10 03:00:52]   Product:      Steam Controller Puck

[2026-06-10 03:01:13] Steam controller device closed after HID IO failure
[2026-06-10 03:01:13]   Product:      Steam Controller Puck

Earlier in the same logs, Steam sometimes reports:

Firmware Version: 0

and sometimes:

Firmware Version: 1780011095

So the firmware updater reports completion, but the HID IO failures persist afterwards.

Wwbwqq 2026-07-30 github

Any news about this? Is the issue being worked on? Two months later, and the problem persists. Updated the controller and it is still basically unusable in wirelessly.

Wwbwqq 2026-08-08 github

Some more logs from the crash

Source:

~/.local/share/Steam/logs/console_log.txt
journalctl

Captured immediately after the failure.

Steam client build: 1785799196
Steam PID: 15484
Controller receiver: Valve Steam Controller Puck
USB ID: 28de:1304
Breakpad CrashID: bp-d284c0d3-f482-4e0e-9ba8-d97bc2260807

Relevant console log:

[2026-08-07 14:40:07] GameAction [...] : LaunchApp changed task to SynchronizingControllerConfig with ""
[2026-08-07 14:40:08] Controller slots reset
[2026-08-07 14:40:08] Warning: failed to set thread priority: set failed for 8: setpriority() failed

[2026-08-07 14:40:08] Unhandled output event type 25705.
[2026-08-07 14:40:08] Unhandled output event type 29557.
[2026-08-07 14:40:08] Unhandled output event type 2617.
[2026-08-07 14:40:08] Warning: Dropped remote output event (tried to read 16, read 0)
[2026-08-07 14:40:08] Unhandled output event type 26995.
[2026-08-07 14:40:08] Warning: Dropped remote output event (tried to read 16, read 0)
...
[2026-08-07 14:40:08] Warning: Dropped remote output event (tried to read 16, read 15)
[2026-08-07 14:40:08] Unhandled output event type 29806.
[2026-08-07 14:40:08] Warning: Dropped remote output event (tried to read 16, read 5)

[2026-08-07 14:40:08] KeyValues Error: LoadFromBuffer: missing { (current key: 'gurations') in file file [offset: 19]

[2026-08-07 14:40:08] src/tier1/KeyValues.cpp (3176) : Assertion Failed: Error while parsing text KeyValues for resource file

[2026-08-07 14:40:08] KeyValues Error: LoadFromBuffer: missing { (current key: 'gurations') in file In Game Actions [offset: 19]

[2026-08-07 14:40:08] src/tier1/KeyValues.cpp (3176) : Assertion Failed: Error while parsing text KeyValues for resource In Game Actions

Journal / Breakpad:

Aug 07 14:40:08 fedora43 steam[15393]: assert_20260807144008_99.dmp[17680]: Uploading dump (out-of-process)
Aug 07 14:40:08 fedora43 steam[15393]: /tmp/dumps/assert_20260807144008_99.dmp

Aug 07 14:40:11 fedora43 assert_20260807144008_99.dmp[17680]: Finished uploading minidump (out-of-process): success = yes
Aug 07 14:40:11 fedora43 assert_20260807144008_99.dmp[17680]: response: CrashID=bp-d284c0d3-f482-4e0e-9ba8-d97bc2260807

Ii-h8-github 2026-08-27 github

Same issue here.

Upstream links

ValveSoftware/steam-for-linux/issues/4127x1 2026-05