* Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
@ 2022-12-19 16:52 Jim Reisert AD1C
2022-12-19 20:59 ` Jon Turney
2022-12-19 21:05 ` Ken Brown
0 siblings, 2 replies; 5+ messages in thread
From: Jim Reisert AD1C @ 2022-12-19 16:52 UTC (permalink / raw)
To: The Cygwin Mailing List
I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
Cygwin" and in addition the X package refresh. I started emacs-X11 in
an xterm and am now seeing this in the console:
Xlib: sequence lost (0x10000 > 0x16c) in reply type 0x13!
Xlib: sequence lost (0x10000 > 0x172) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x17f) in reply type 0xf!
Xlib: sequence lost (0x10000 > 0x185) in reply type 0x1c!
Xlib: sequence lost (0x10000 > 0x1ba) in reply type 0xf!
Xlib: sequence lost (0x10000 > 0x519) in reply type 0xf!
Did something go awry with the update?
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://ad1c.us
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
2022-12-19 16:52 Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13! Jim Reisert AD1C
@ 2022-12-19 20:59 ` Jon Turney
2022-12-19 23:44 ` Jim Reisert AD1C
2022-12-19 21:05 ` Ken Brown
1 sibling, 1 reply; 5+ messages in thread
From: Jon Turney @ 2022-12-19 20:59 UTC (permalink / raw)
To: Jim Reisert AD1C, The Cygwin Mailing List
On 19/12/2022 16:52, Jim Reisert AD1C via Cygwin wrote:
> I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
> Cygwin" and in addition the X package refresh. I started emacs-X11 in
> an xterm and am now seeing this in the console:
>
> Xlib: sequence lost (0x10000 > 0x16c) in reply type 0x13!
> Xlib: sequence lost (0x10000 > 0x172) in reply type 0x1c!
> Xlib: sequence lost (0x10000 > 0x17f) in reply type 0xf!
> Xlib: sequence lost (0x10000 > 0x185) in reply type 0x1c!
> Xlib: sequence lost (0x10000 > 0x1ba) in reply type 0xf!
> Xlib: sequence lost (0x10000 > 0x519) in reply type 0xf!
>
> Did something go awry with the update?
This seems to be an upstream problem with libX11 1.8.3
I've withdrawn that version (so setup should automatically downgrade to
the previous version, 1.8.1)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
2022-12-19 20:59 ` Jon Turney
@ 2022-12-19 23:44 ` Jim Reisert AD1C
0 siblings, 0 replies; 5+ messages in thread
From: Jim Reisert AD1C @ 2022-12-19 23:44 UTC (permalink / raw)
To: The Cygwin Mailing List
On Mon, Dec 19, 2022 at 1:59 PM Jon Turney wrote:
> This seems to be an upstream problem with libX11 1.8.3
>
> I've withdrawn that version (so setup should automatically downgrade to
> the previous version, 1.8.1)
Thank you, Jon.
Yes Ken, the problems show up in Emacs 28.2
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://ad1c.us
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
2022-12-19 16:52 Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13! Jim Reisert AD1C
2022-12-19 20:59 ` Jon Turney
@ 2022-12-19 21:05 ` Ken Brown
2022-12-19 21:09 ` Ken Brown
1 sibling, 1 reply; 5+ messages in thread
From: Ken Brown @ 2022-12-19 21:05 UTC (permalink / raw)
To: cygwin
On 12/19/2022 11:52 AM, Jim Reisert AD1C via Cygwin wrote:
> I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
> Cygwin" and in addition the X package refresh. I started emacs-X11 in
> an xterm and am now seeing this in the console:
>
> Xlib: sequence lost (0x10000 > 0x16c) in reply type 0x13!
> Xlib: sequence lost (0x10000 > 0x172) in reply type 0x1c!
> Xlib: sequence lost (0x10000 > 0x17f) in reply type 0xf!
> Xlib: sequence lost (0x10000 > 0x185) in reply type 0x1c!
> Xlib: sequence lost (0x10000 > 0x1ba) in reply type 0xf!
> Xlib: sequence lost (0x10000 > 0x519) in reply type 0xf!
>
> Did something go awry with the update?
These messages are probably the result of the update of libX11. I know the
messages are annoying, but I'd advise you to ignore them unless you're seeing
actual problems with emacs.
Nevertheless, there are a couple of things that I'll try when I get a chance.
One is to rebuild emacs against the new libX11. The other is to see if the
problem still exists in the current emacs development tree.
Ken
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
2022-12-19 21:05 ` Ken Brown
@ 2022-12-19 21:09 ` Ken Brown
0 siblings, 0 replies; 5+ messages in thread
From: Ken Brown @ 2022-12-19 21:09 UTC (permalink / raw)
To: cygwin
On 12/19/2022 4:05 PM, Ken Brown via Cygwin wrote:
> On 12/19/2022 11:52 AM, Jim Reisert AD1C via Cygwin wrote:
>> I just updated Cygwin to "3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64
>> Cygwin" and in addition the X package refresh. I started emacs-X11 in
>> an xterm and am now seeing this in the console:
>>
>> Xlib: sequence lost (0x10000 > 0x16c) in reply type 0x13!
>> Xlib: sequence lost (0x10000 > 0x172) in reply type 0x1c!
>> Xlib: sequence lost (0x10000 > 0x17f) in reply type 0xf!
>> Xlib: sequence lost (0x10000 > 0x185) in reply type 0x1c!
>> Xlib: sequence lost (0x10000 > 0x1ba) in reply type 0xf!
>> Xlib: sequence lost (0x10000 > 0x519) in reply type 0xf!
>>
>> Did something go awry with the update?
>
> These messages are probably the result of the update of libX11. I know the
> messages are annoying, but I'd advise you to ignore them unless you're seeing
> actual problems with emacs.
>
> Nevertheless, there are a couple of things that I'll try when I get a chance.
> One is to rebuild emacs against the new libX11. The other is to see if the
> problem still exists in the current emacs development tree.
Never mind. See Jon's reply.
Ken
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-12-19 23:44 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-19 16:52 Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13! Jim Reisert AD1C
2022-12-19 20:59 ` Jon Turney
2022-12-19 23:44 ` Jim Reisert AD1C
2022-12-19 21:05 ` Ken Brown
2022-12-19 21:09 ` Ken Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).