Steam crashes after connecting xbox 360 controller
I have a similar issue here with the same controller IDs on Fedora 42. Steam crashes when inserting the controller while steam is running or on launch while the controller is connected. dmesg reports a segfault:
CSteamControlle[7103]: segfault at 0 ip 0000000000000000 sp 00000000d34fc6dc error 14 likely on CPU 5 (core 5, socket 0)
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
My libX11 versions are:
libX11.i686 1.8.13-1.fc42
libX11.x86_64 1.8.13-1.fc42
but I'm using Wayland though. This controller has worked in Steam before, but I haven't used it in a while.
It might be because gnome removed all x11 components,and steam is mainly tested on kde plasma
I should not crash though regardless. My impression is: X11 is more or less dead and most distros have moved or will move to Wayland.
I should not crash though regardless. My impression is: X11 is more or less dead and most distros have moved or will move to Wayland.
I found it, xtest is extension in gnome mutter,you can enable it by dconf and remote desktop also needs to be on in dconf,it worked for me
I should not crash though regardless. My impression is: X11 is more or less dead and most distros have moved or will move to Wayland.
I found it, xtest is extension in gnome mutter,you can enable it by dconf and remote desktop also needs to be on in dconf,it worked for me
Sounds good. Could you elaborate where to enable/disable what?
I'll leave this here for people having problems. Remove Xtest from xwayland-disable-extension in dconf /org/gnome/mutter/wayland.
Nothing extracted yet.
Your system information
Steam client version 1769025840
CachyOS (arch - Gnome):
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Steam Logs: steam-logs.tar.gz
GPU: AMD
Please describe your issue in as much detail as possible:
I connect my controller : Bus 001 Device 007: ID 045e:028e Microsoft Corp. Xbox360 Controller
it crashes my already running steam client. What i know is this issue is new because one, it is just that i have connected my controller after a while which previously worked , as i have searched it has something to do with the libx11's newer versions . and the controller is a 'evofox elite X RGB pc wired gamepad'.
Steps for reproducing this issue: