| 1 |
On 2023-01-26, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 2 |
> A recent xlib update to 1.8.3 seems to have cause some applications |
| 3 |
> (e.g. emacs) to dribble out messages like this while they are running: |
| 4 |
> |
| 5 |
> Xlib: sequence lost (0x10000 > 0x45e) in reply type 0x1c! |
| 6 |
> Xlib: sequence lost (0x10000 > 0x464) in reply type 0x1c! |
| 7 |
> Xlib: sequence lost (0x10000 > 0x471) in reply type 0x1c! |
| 8 |
> Xlib: sequence lost (0x10000 > 0x476) in reply type 0x1c! |
| 9 |
> Xlib: sequence lost (0x10000 > 0x483) in reply type 0x1c! |
| 10 |
> Xlib: sequence lost (0x10000 > 0x53a) in reply type 0xf! |
| 11 |
> Xlib: sequence lost (0x10000 > 0x1139) in reply type 0xc! |
| 12 |
> |
| 13 |
> Posts in varioius fora imply that this is a bug in xlib 1.8.3: |
| 14 |
> |
| 15 |
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026809 |
| 16 |
> https://www.linuxquestions.org/questions/slackware-14/spurious-stderr-error-messages-with-libx11-1-8-3-x86_64-1-a-4175719999/ |
| 17 |
> |
| 18 |
> Did this buggy version lib libx11 make it into gentoo stable? |
| 19 |
|
| 20 |
Apparently yes. |
| 21 |
|
| 22 |
I see that today's sync/update has just downgraded libX11 to 1.8.1, and |
| 23 |
the problem went away. |
| 24 |
|
| 25 |
-- |
| 26 |
Grant |
Archives