You are not logged in.
Trying to run Wurm Online with the steam launcher and the latest libx11 causes an error:
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x7!
Xlib: sequence lost (0x10000 > 0x2ad) in reply type 0x8!
This type of output is spammed when running steam in console mode to observe the stdout.
Downgrading to libx11 1.8.2-2 solves the issue for now. We'll probably need someone to figure out what is causing a conflict between the new libx11 and steam for this to be resolved.
Last edited by mavrent (2022-12-18 19:14:15)
Offline
Fixed as of libx11 1.8.3-3
Offline
Fixed as of libx11 1.8.3-3
Well, I dont think this problem is solved by 1.8.3-3.
My `terminator` can not response my key press with this error under libx11-1.8.3-3.
I'm using libx11-1.8.1-3 now ....
Offline
mavrent wrote:Fixed as of libx11 1.8.3-3
Well, I dont think this problem is solved by 1.8.3-3.
My `terminator` can not response my key press with this error under libx11-1.8.3-3.
I'm using libx11-1.8.1-3 now ....
I agree - for me it does not seems to be fixed either. Actually none of Steam games were able to start after upgrade to 1.8.3-3. So I fixed it by rolling back to 1.8.2-2 and freezing libx11 on that version.
Offline
I have the same issue, however only when using Radeon instead of Intel Graphics. Hope this is fixed soon.
Offline
There's possibly 2 versions lib32-libx11 and libx11 installed respectively for 32 and 64 bits. Currently only the 32 bits in version 1.8.3-1 is an issue. The current libx11 in version 1.8.3-6 works correctly.
Downgrading lib32-libx11 to 1.8.2-2 did solve the issue for me.
sudo pacman -U https://archive.archlinux.org/packages/l/lib32-libx11/lib32-libx11-1.8.2-2-x86_64.pkg.tar.zst
Last edited by milto (2023-02-02 15:54:02)
Offline
Downgrading lib32-libx11 to 1.8.2-2 did solve the issue for me.
sudo pacman -U https://archive.archlinux.org/packages/l/lib32-libx11/lib32-libx11-1.8.2-2-x86_64.pkg.tar.zst
Thanks, this fixes the issue for me as well!
Offline