I see this symptom on my Fedora 38 AMD Ryzen system - 14 separate windows containing bits of the steam UI after monitor off overnight.
Running
killall steamwebhelper
recovers the steam client back to a usable state.
Computer Information:
Manufacturer: AZW
Model: SER
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 5560U with Radeon Graphics
CPU Family: 0x19
CPU Model: 0x50
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4060 MHz
12 logical processors
6 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Fedora Linux 38 (Workstation Edition) (64 bit)
Kernel Name: Linux
Kernel Version: 6.3.4-201.fc38.x86_64
X Server Vendor: The X.Org Foundation
X Server Release: 12201009
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20230509.49499
Video Card:
Driver: AMD AMD Radeon Graphics (renoir, LLVM 16.0.4, DRM 3.52, 6.3.4-201.fc38.x86_64)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.1.1
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x1638
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.08" x 11.42" (23.07" diag), 51.0cm x 29.0cm (58.6cm diag)
Primary VRAM: 3072 MB
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Whenever a window or a notification popup is created when there is no display available, the steam client "crashes". Actually I think it is not a crash, but the client turns into an unusable state.
I have three displays setup, but I suspect the number of display are irrelevant. Whenever I go AFK I turn off my monitors, when I return to my desktop and turn back on the monitors, most of the times the steam client is "crashed".
Here is a normal
xrandroutput:And this is
xrandrwith two monitors powered off:My guess is that when creating a new chat window, a notification window, or any kind of new window, the steam client tries to obtain the displays available such as provided by
randrand somehow it fails to create a new window and crashes.Here is the desktop state whenever I turn back on the monitor:

Same, but with the steam client windows unstacked.

Looks like an independent window is created for every popup menu and stacked over the main client window.
I have attached several logs which include some debug on the crash:
steamui_html.txt
steamwebhelper.log
webhelper.txt
Steps for reproducing this issue:
Other notes: