godot: Crash on Linux after libX11 update with: [xcb] Unknown sequence number while processing queue (libX11 1.8.3 or 1.8.2 + X-IfEvent patch)

Fixed [Archlinux], I had to install downgrade with:

$ paru -Syu --noconfirm downgrade

$ sudo downgrade libx11

-> and select the version libx11-1.8.2-2

It would be pretty interesting, if the issue was solved for you. I’m running libX11 1.8.6-1 (Arch Linux) as well and unfortunately I’m still experiencing those crashes. Please let us know if the problems still persist for you or not. Maybe it’s another component or the interaction of components that has to be taken into consideration to resolve those crashes once and for all.

Thanks everyone for the reports!

I believe the issue has been properly fixed in upstream libx11 now (for a future 1.8.4 release), and most Linux distros seem to be aware of the issues with 1.8.2 and 1.8.3 and have found ways to mitigate them:

• Stick to 1.8.1 for now (OpenSUSE, Fedora). For Fedora, 1.8.3 without MR 176 was proposed as update candidate but is currently on hold due to those very issues: https://bodhi.fedoraproject.org/updates/FEDORA-2023-be3023012d - it’s however in Rawhide so you might experience the bug there.
• Update to 1.8.3 + upstream MR 176 and 180 (Arch, Gentoo, Mageia).

So let’s close 😃

Edit: 1.8.4 has been released and confirmed to fix this issue.

Unrelated, but that patch also makes the same crash on gamescope. So it’s not just godot

libx11 now at 1.8.3-5 on Arch. Everything works so far on Godot 4 beta 10.

I’m still randomly getting crashes during editor use on fully updated arch linux and godot 4.0 beta 10 / current master dev build.

> bin/godot.linuxbsd.editor.dev.x86_64
Godot Engine v4.0.beta.custom_build.f05fe7454 - https://godotengine.org
OpenGL Renderer: Mesa Intel(R) HD Graphics 620 (KBL GT2)
 
Editing project: /home/...[removed]
Godot Engine v4.0.beta.custom_build.f05fe7454 - https://godotengine.org
Vulkan API 1.3.230 - Using Vulkan Device #0: Intel - Intel(R) HD Graphics 620 (KBL GT2)

later various types of crashes with xcb:

[xcb] Unknown request in queue while dequeuing
[xcb] You called XInitThreads, this is not your fault
[xcb] Aborting, sorry about that.
godot.linuxbsd.editor.dev.x86_64: xcb_io.c:175: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.

or

godot.linuxbsd.editor.dev.x86_64: xcb_in.c:757: xcb_request_check: Assertion `!reply' failed.

or

[xcb] Unknown sequence number while processing queue
[xcb] You called XInitThreads, this is not your fault
[xcb] Aborting, sorry about that.
godot.linuxbsd.editor.dev.x86_64: xcb_io.c:278: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

is this the same issue or something related. I haven’t yet tried downgrading libx11 (It’s currently arch 1.8.3-3, which should be already fixed)

Alternatively, you can also run

sudo pacman -U https://archive.archlinux.org/packages/l/libx11/libx11-1.8.2-2-x86_64.pkg.tar.zst

Just remember to add libx11 to the ignore list

This issue has been reported in numerous other places, and seems to have been fixed just an hour ago as of writing this

https://github.com/ValveSoftware/Dota-2/issues/2218 https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/176 https://bugs.archlinux.org/task/76860#comment213715

Correction: A PR with a fix opened an hour ago

opensuse have already fixed it as of 5 hours ago https://build.opensuse.org/package/show/openSUSE:Factory/libX11

@Riteo Using several programs on X11 and I haven’t noticed any other issues, it looks like only Godot is affected by this update to OpenSuse Tumbleweed.

@Megalomaniak without XWayland the X11 code wouldn’t run close at all to the problematic part (it’d fail waaaay earlier), so I presume that everyone stumbling on this issue already has it installed.

Yeah we should wait for an official upstream fix to be consistently deployed to all distros before closing. Despite it being open we had 5 duplicate bug reports, 2 of them even after we’ve pinned this issue.

But there’s nothing to do from our side, this is just open for user information.

It’s “fixed” by distros (Arch) patching in PRs that aren’t merged upstream yet (and might not even get merged) because they make crashes elsewhere, so this issue should probably stay open until it works without every distro rolling up their own patches

Assuming ‘note sure’ is a typo for ‘not sure’?

Anyway good to see it’s fixed

Either that, or a bug in the problematic libX11 commit. Or in the very worst case, both. Not sure I would agree with a patch in libX11 breaking (crashing) existing programs is the right thing to do, even if it expose some problem in said programs.

lib32-libx11 1.8.3-1.0 update that I was greeted with this morning on Manjaro Testing seems to have resolved it for me.

Arch Linux users, please comment on https://bugs.archlinux.org/task/76860 which is the upstream report.

1.8.3-4 removed the (yet unmerged) upstream patches that solve the issue, to replace them with a (merged) upstream patch. They seem to expect it fixes Godot too, but evidently it doesn’t. https://github.com/archlinux/svntogit-packages/commit/27567a0220da86d3c45eb3e341f30457f93d99d7

Looks like on arch it is already fixed

Yup. Tested Godot_v4.0-beta8_mono_linux_x86_64 with libx11 1.8.3-3 and the issue seems to be fixed.