FS#77033 - [lib32-libx11] 1.8.3: "Xlib: sequence lost" around Steam and games crashing randomly

Attached to Project: Community Packages
Opened by Dominik Grzywak (StarterX4) - Saturday, 07 January 2023, 17:08 GMT
Last edited by Toolybird (Toolybird) - Sunday, 21 May 2023, 06:53 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Laurent Carlier (lordheavy)
Felix Yan (felixonmars)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Description:
After updating lib32-libx11 to the 1.8.3, Steam started to spam the terminal with such an output:
"Xlib: sequence lost (0x10000 > 0x1043) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x1050) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x105d) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x1064) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x106f) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x107c) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x1089) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x1096) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x10a3) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x10aa) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x10b5) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x10eb) in reply type 0xc!
Xlib: sequence lost (0x10000 > 0x1119) in reply type 0xc!"

And the games like L4D2 or TF2 started crashing randomly, and usually in 5-10 mins since launch.
Downgrading to 1.8.2 fixed the issue.

It seems to happen also with Dota 2:
https://github.com/ValveSoftware/Dota-2/issues/2229
https://github.com/ValveSoftware/Dota-2/issues/2218

Additional info:
* package version(s)
1.8.3-1
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
1. Have a lib32-libx11 1.8.3-1
2. Launch Steam in terminal (to see the output)
3. Try to play Left 4 Dead 2 or Team Fortress 2, according to the found bug reports, also Dota 2.
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 21 May 2023, 06:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  lib32-libx11 1.8.4-1
Comment by loqs (loqs) - Saturday, 07 January 2023, 17:32 GMT
It is reported applying the same patches as in libx11 1.8.3-5 resolves the issue [1].

[1] https://bbs.archlinux.org/viewtopic.php?pid=2078190#p2078190
Comment by Neko-san (Neko-san) - Monday, 16 January 2023, 14:21 GMT
This is the upstream issue report, which supposedly already has a fix merged; hopefully we can get that fix soon.

https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/174
Comment by blueman (blueman) - Monday, 23 January 2023, 11:52 GMT
libx11 has this fix already included, but lib32-libx11 is missing it: https://github.com/archlinux/svntogit-packages/blob/packages/libx11/trunk/0001-Revert_Update_XPutBackEvent.diff
Comment by Toolybird (Toolybird) - Monday, 23 January 2023, 18:43 GMT
Dupe  FS#77240 
Comment by No (MiiMe19) - Wednesday, 15 February 2023, 23:10 GMT
Any information on when a build may possibly be completed for this, given that the bug is over a month old now?
Comment by Laurent Carlier (lordheavy) - Thursday, 16 February 2023, 08:34 GMT
lib32-libx11-1.8.4-1 pushed in multilib

Loading...