Hello @in-rainbows-1, can you check if any 32 bit OpenGL application like glxinfo32 from lib32-mesa-utils works? We've seen BadValue (integer parameter out of range for operation) before with an incomplete video driver install. In general, the NVIDIA proprietary driver needs the video driver's running kernel module, 32 bit userspace libraries, and 64 bit userspace libraries to all be installed and exactly the same version to work.
Thanks, glxinfo32 did show 32 bit applications were broken system wide. My GPU was getting updates from the AUR and I had a version mismatch.
Nothing extracted yet.
My system information
Steam client version: 1778281814 (built May 8 2026)
Distribution: EndeavourOS (Arch-based), Linux 7.0.3-arch1-2, KDE Plasma 6.6.4
Opted into Steam client beta?: No
Have you checked for system updates?: Yes — system is fully up to date
Steam Logs: attached
GPU: NVIDIA GeForce GTX 1060 6GB, driver 580.142 (DKMS)
After the May 8, 2026 client update, Steam crashes immediately on launch with a SIGSEGV in vgui2_s.so. The updater also throws SteamUpdateUI: An X Error occurred / BadValue (integer parameter out of range for operation) during every launch attempt. The main Steam process segfaults at vgui2_s.so -> steamui.so -> libc, with XOpenIM() failed and XRRGetOutputInfo Workaround logged immediately before the crash. A minidump was submitted to Valve's crash server: CrashID=bp-d0b19252-05c0-47c6-9e9b-5f20c2260509. Steam was working normally prior to this update with no system changes made that day beyond a routine pacman -Syu.
Steps for reproducing this issue:
Launch Steam on a Wayland session (KWin/XWayland) with an NVIDIA GPU
Observe updater window throwing BadValue X error
Steam segfaults before the main window opens
steam-logs.tar.gz