Bug#1031697: libx11-xcb1: Please update to 1.8.4 - Apps crashing under wayland due to bugs caused by patches in 1.8.3
Package: libx11-xcb1
Version: 2:1.8.3-3
Severity: important
Tags: upstream
X-Debbugs-Cc: stephanlachnit@debian.org, tjaalton@debian.org
Dear Developer,
Could You please update the package to the new upstream version of 1.8.4
The new version 1.8.4 has been months in the making and it fixes significant bugs [1] that also affect
gamescope on wayland usage (both the current versions already and Debian and the upcoming upstream).
It is a maintenance update with no ABI change, so no transition necessary...
When trying to run app through gamescope on KDE Plasma Wayland and GNOME Wayland, the types of crashes occurs:
For example:
gamescope -H 1080 -f -- env MESA_LOADER_DRIVER_OVERRIDE=zink MANGOHUD=1 gamemoderun ./heaven
The crash message:
heaven_x64: ../../src/xcb_in.c:757: xcb_request_check: Assertion `!reply' failed.
(EE) failed to read Wayland events: Broken pipe
browser_x64: Fatal IO error: client killed
It would be a shame for the Bookworm not to have this fixed...
I have tested/rebuilt the Debian 1.8.3 source without these two patches:
0003-Revert-Fix-797755-Allow-X-IfEvent-to-reenter-libX11.patch
0004-Revert-Allow-X-IfEvent-to-reenter-libX11.patch
And the bug is fixed! It seems that the newly released libx11 1.8.4 version fixes this bug.
Kind regards,
Safir
[1] https://github.com/godotengine/godot/issues/69352
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.12-3-liquorix-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libx11-xcb1 depends on:
ii libx11-6 2:1.8.3-3
libx11-xcb1 recommends no packages.
libx11-xcb1 suggests no packages.
-- no debconf information
Reply to: