On 2023-01-26, Grant Edwards <[email protected]> wrote: > A recent xlib update to 1.8.3 seems to have cause some applications > (e.g. emacs) to dribble out messages like this while they are running: > > Xlib: sequence lost (0x10000 > 0x45e) in reply type 0x1c! > Xlib: sequence lost (0x10000 > 0x464) in reply type 0x1c! > Xlib: sequence lost (0x10000 > 0x471) in reply type 0x1c! > Xlib: sequence lost (0x10000 > 0x476) in reply type 0x1c! > Xlib: sequence lost (0x10000 > 0x483) in reply type 0x1c! > Xlib: sequence lost (0x10000 > 0x53a) in reply type 0xf! > Xlib: sequence lost (0x10000 > 0x1139) in reply type 0xc! > > Posts in varioius fora imply that this is a bug in xlib 1.8.3: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026809 > https://www.linuxquestions.org/questions/slackware-14/spurious-stderr-error-messages-with-libx11-1-8-3-x86_64-1-a-4175719999/ > > Did this buggy version lib libx11 make it into gentoo stable?
Apparently yes. I see that today's sync/update has just downgraded libX11 to 1.8.1, and the problem went away. -- Grant
