protonscr

crashes and unable to launch any games after a while of playing, eventually crashing X

steamopen Distro Family: Arch
ValveSoftware/steam-for-linux#9083 · opened 2023-01-08 by deergoduc · updated 2023-01-13 · 7 comments · github
Ddeergoduc 2023-01-08 github

Your system information

  • Steam client version (build number or date): 2023-01-08T23:58Z, Steam packages version 1671236931
  • Distribution (e.g. Ubuntu): Arch Linux
  • Opted into Steam client beta?: [Yes/No] No
  • Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

Immediately after launching steam, i get the following errors:
Xlib: sequence lost (0x10000 > 0x3705) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x3706) in reply type 0xc!

At first, only a bunch of these appears, but over time, the frequency increases.
Launching any game, as well as opening the in-game overlay, or any chat windows, causes more to appear, after a while games start to crash, and trying to launch any other games doesn't work, they either crash immediately, or don't open at all.
Restarting steam doesn't help, the errors start appearing again at the same frequency.
Leaving it for a while, X crashes.

Steps for reproducing this issue:

1.Run Steam
2.Open any game, and leave it open for some time

Kkisak-valve maintainer 2023-01-08 github

Hello @deergoduc, there's a known upstream regression in libX11 1.8.3 which manifests as Xlib: sequence lost (0x10000 > 0x3705) in reply type 0xc!. Can you reproduce this issue with libx11 (and lib32-libx11) 1.8.2 or 1.8.1?

Ddeergoduc 2023-01-09 github

Downgraded libx11, unfortunately the issue persists. Tried 1.8.2-2, 1.8.1-3.

Ssoerengrunewald 2023-01-09 github

Same on Fedora 37, running 1.8.3-1

Aagurenko 2023-01-09 github

Same on Fedora 37, running 1.8.3-1

same here on F37, downgrade to libX11-1.8.1-2.fc37.x86_64 helped

Ddeergoduc 2023-01-10 github

Downgraded libx11, unfortunately the issue persists. Tried 1.8.2-2, 1.8.1-3.

I double-checked, and it seems I either forgot to also downgrade lib32-libx11, or did something wrong while doing it.
After downgrading lib32-libx11 to 1.8.2-2, it works fine.

PPatola 2023-01-11 github

Hello @deergoduc, there's a known upstream regression in libX11 1.8.3 which manifests as Xlib: sequence lost (0x10000 > 0x3705) in reply type 0xc!. Can you reproduce this issue with libx11 (and lib32-libx11) 1.8.2 or 1.8.1?

Is this the regression? https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/176

Xxpander69 2023-01-13 github

Downgraded libx11, unfortunately the issue persists. Tried 1.8.2-2, 1.8.1-3.

you need to downgrade lib32-libx11
this fixes the log spam for me

edit: Sorry didn't notice your other comment. You already figured out :)

Nothing extracted yet.