Yesterday, I was facing this issue on AMD drivers (RADV/vulkan-radeon, not AMDVLK) as well. I was on the July 5 version of the Steam client beta, if it helps.
I update my packages every evening just before shutting my computer down, and the packages that were updated the day before the issue started happening were the Linux kernel (updated to version 6.4.1) and libxml2 (updated to version 2.11.4, though I doubt it's relevant as the Steam binary doesn't seem to depend on it).
I can't reproduce the issue to gather logs anymore, though, because yesterday evening's package update led to Steam now facing #9805.
Yesterday, I was facing this issue on AMD drivers (RADV/
vulkan-radeon, not AMDVLK) as well. I was on the July 5 version of the Steam client beta, if it helps.I update my packages every evening just before shutting my computer down, and the packages that were updated the day before the issue started happening were the Linux kernel (updated to version 6.4.1) and libxml2 (updated to version 2.11.4, though I doubt it's relevant as the Steam binary doesn't seem to depend on it).
I can't reproduce the issue to gather logs anymore, though, because yesterday evening's package update led to Steam now facing #9805.
Seems to be a fair amount of issues around the 6.4.1 kernel and latest Nvidia drivers. But you're on AMD and having the same issue which seems to lead back to either AMD or Steam but it's hard to pin point because I don't see much in the system logs.
Now that I got rid of the libgudev problem, let's see if this issue still happens, though I'm now on kernel version 6.4.2.
I wonder if this isn't related to my issue as well. It's slightly different for me, however.
I'm running Ubuntu Studio 22.04 with an nVidia 3080 Ti and after the new Steam client was released I noticed issues. I was playing CP2077 and my FPS dropped to 12. Some digging found that what appears to be happening is the Steam client leaks resources into Xorg which causes Xorg to constantly use more and more VRAM in the GPU. I've seen it get as high as 8GB of VRAM used by Xorg (with no games running).
Restarting the Steam client causes Xorg to release those resources as well as the VRAM used and it will drop back down to 400-500MB (what appears to be the normal amount).
I wonder if what is happening with the Xorg crash is it's using all the VRAM. I've never let it get that far so I can't say for certain that's the issue here.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
I realize that Steam is an OpenGL program and shouldn't be capable of taking down the display server or system. So first thought was nvidia drivers - I did a couple tests and launched games through Lutris and couldn't replicate the problem. So back to steam(?). I can't pin point if it's Steam in general or the overlay, because it locks up X randomly, but only if Steam is running.
Symptom 1: booted os -> launched terminal and firefox, waited 10 minutes -> launched Steam -> System cripples to a hault, taking 30 seconds to respond to any input -> switch to TTY2 and
killall steam-> switch back to TTY1 and problem gone.Symptom 2: launch game -> system unresponsive to any input (can't kill game or even window manager). had to switch to TTY2 and
killall steamto recover.Symptom 3: launch game -> launch overlay -> system unresponsive but this time I could not switch TTY's, no input recognized.
Steps for reproducing this issue:
killall steamEdit: I should note killing the game PID alone did not recover the system. I had to kill steam.
Edit 2: Just happened again when opening a group chat from the overlay in game.