From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
Date: Mon, 19 Dec 2022 16:09:23 -0500 [thread overview]
Message-ID: <a6df508e-f857-6a93-e537-5c89668cf39b@cornell.edu> (raw)
In-Reply-To: <0e870dca-7d20-cfa1-33c7-0b29c0444245@cornell.edu>
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
prev parent reply other threads:[~2022-12-19 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 16:52 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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6df508e-f857-6a93-e537-5c89668cf39b@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).