Hello @kisak-valve
https://gist.github.com/duramuss/5395592c03f7def472632cc41cc4d8b4

I'm having the same issue on Ubuntu 20.04.6.

Same thing happening on Arch
Linux computer 6.2.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 22 Mar 2023 22:52:35 +0000 x86_64 GNU/Linux
nvidia/530.41.03
same steam version.
NVIDIA GeForce RTX 3080 Ti
Driver: nvidia 530.41.03

I can confirm this on Manjaro

Steam Package versions: 1679680416 (same version)

Operating System Version:
"Manjaro Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.2.9-1-MANJARO

Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 530.41.03

I confirm this issue on Debian 11: game properties just displays a white window.

Unable to run most of Steam games: they just open a white window (which appears to be some kind of web browser window with a broken rendering, since by moving the mouse around we could see the pointer changing to a hand in some areas)

Steam Package version: 1679680416
Distribution: Debian 11
Kernel: 6.2.8-100 x86_64
GPU: NVIDIA GeForce RTX 3060 (Driver Version: 530.41.03)

Just to follow-up on this issue, I just checked with the beta version, it's even worse: can't see the list of games (just a white frame). I reverted to the stable Steam release (1679680416) and then tried downgrading the nvidia drivers to version 525.89.02 (instead of 530.41.03). Exactly the same issue (white window when trying to open game properties or to launch a game, game does not start, probably waiting for an input from the user): the regression has been introduced by the Steam client, not by updated nvidia drivers.

It's not the nvidia drivers, i am on Intel HD graphics and affected by the same issue.

Same issue for me.

tried disabling Smooth Scrooling and GPU accelerated rendering, but they don't have a effect on it either ;(

Is there any way to downgrade to an older Steam version? Since it worked fine in the last version

Any news on this? Haven't seen anything else anywhere. My steam has updated two times since this started and it's still has the problem.

This issue persists with Steam Package version: 1682573004.
Still unable to display the properties of any game nor launch games such as Valheim (it just opens a white window)

I was having this issue and was able to resolve / work around it it by running steam with the environment variable QT_X11_NO_MITSHM=1 set. My setup is somewhat unconventional so your mileage may vary.

I was seeing log entries in cef_log.txt after trying to open game properties such as:

[0429/134841.476625:WARNING:xproto_util.cc(51)] X error received: serial 235, error_code 10 (BadAccess (attempt to access private resource denied)), request_code 130, minor_code 1 (X_ShmAttach) [0429/134841.476747:WARNING:xproto_util.cc(51)] X error received: serial 236, error_code 10 (BadAccess (attempt to access private resource denied)), request_code 130, minor_code 1 (X_ShmAttach) [0429/134841.476847:WARNING:xproto_util.cc(51)] X error received: serial 237, error_code 128 (BadShmSeg (invalid shared segment parameter)), request_code 130, minor_code 3 (X_ShmPutImage) [0429/134841.476943:WARNING:xproto_util.cc(51)] X error received: serial 238, error_code 128 (BadShmSeg (invalid shared segment parameter)), request_code 130, minor_code 3 (X_ShmPutImage) [0429/134841.477133:WARNING:xproto_util.cc(51)] X error received: serial 240, error_code 128 (BadShmSeg (invalid shared segment parameter)), request_code 130, minor_code 2 (X_ShmDetach) [0429/134841.477218:WARNING:xproto_util.cc(51)] X error received: serial 241, error_code 128 (BadShmSeg (invalid shared segment parameter)), request_code 130, minor_code 2 (X_ShmDetach)

I am running steam inside an LXC container, so the X MIT SHM extension apparently doesn't work between the container and the base system's X server.

After getting it to work I note that the current release client has new/updated UI (similar to the beta client look and feel) for the properties window; related?

Somewhat related as well, but the beta client does not render at all unless i also run it with QT_X11_NO_MITSHM=1 set.

Kernel: 6.3.0-gentoo
NVIDIA Driver: 525.105.17

Steam client version: 1682708537
Distribution: Gentoo (base system and container)
Opted into Steam client beta?: No; but see above
Have you checked for system updates?: Yes

Good job tehkab!

Steam here is running under systemd-nspawn and setting QT_X11_NO_MITSHM=1 fixes the issue. I guess all people here are running steam in containers too.

Thanks a lot @tehkab, setting the environment variable QT_X11_NO_MITSHM=1 solved the issue for me too!

Thank you @tehkab

This solved the issue for me too. I'm running steam in a systemd-nspawn container.

Interestingly a buddy of mine is also running steam inside an nspawn container and he doesn't have the issue at all. The only obvious difference between our setups is, that he uses an AMD GPU.

It seems to be fixed on my end with one of the later updates, can anyone who had the issue confirm that?

I still get the white box when I open the game properties window and don't set the environment variable QT_X11_NO_MITSHM=1 with the latest release version.
With QT_X11_NO_MITSHM=1 it works fine.

QT_X11_NO_MITSHM=1 works for me. I'm running Steam inside a container in Kubernetes cluster

I installed Steam in a nspawn container and directly the login screen render white and could not log in. The env QT_X11_NO_MITSHM=1 helped but I wished I had discovered it earlier saved me a few headaches. Thank you @tehkab