Re: Mailing list subscription problems
On 12/19/22 11:42, Corinna Vinschen via Cygwin wrote: Actually, Google hasn't relaxed their filtering, rather the DNS record of the cygwin.com domain was the culprit. It didn't have the required (by Google) DKIM/SFP records. This has been rectified last week, fortunately, so this shouldn't happen again. I re-enabled mail for all accounts having been disabled due to bounces. Off-topic but I can't resist :-) The real irony here is that while Google has draconian anti-SPAM filtering for _incoming_ mail, they are now one of the leading senders of SPAM, and emails to their abuse address bounce. Sigh! (I'll shut up now) -- Jim Garrison j...@acm.org -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
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, , https://ad1c.us -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
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 (0x1 > 0x16c) in reply type 0x13! Xlib: sequence lost (0x1 > 0x172) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x17f) in reply type 0xf! Xlib: sequence lost (0x1 > 0x185) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x1ba) in reply type 0xf! Xlib: sequence lost (0x1 > 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
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 (0x1 > 0x16c) in reply type 0x13! Xlib: sequence lost (0x1 > 0x172) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x17f) in reply type 0xf! Xlib: sequence lost (0x1 > 0x185) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x1ba) in reply type 0xf! Xlib: sequence lost (0x1 > 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
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 (0x1 > 0x16c) in reply type 0x13! Xlib: sequence lost (0x1 > 0x172) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x17f) in reply type 0xf! Xlib: sequence lost (0x1 > 0x185) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x1ba) in reply type 0xf! Xlib: sequence lost (0x1 > 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) -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Mailing list subscription problems
On 12/19/22 2:42 PM, Corinna Vinschen via Cygwin wrote: On Dec 19 12:50, David Standish via Cygwin wrote: On 12/19/22, Kyle Marek via Cygwin wrote: (CC'd the public mailing list for visibility of problems that may be affecting others) Hello, Today I received an email from cygwin-boun...@cygwin.com with the subject line of "You have been unsubscribed from the Cygwin mailing list". I also just noticed that my Cygwin directory doesn't have any emails since the email identified by the following headers: [...] I've experienced the same problem. I reactivated my subscription a couple times. More cygwin mail has been getting through to me that last few days. Hopefully google has relaxed their filtering, Actually, Google hasn't relaxed their filtering, rather the DNS record of the cygwin.com domain was the culprit. It didn't have the required (by Google) DKIM/SFP records. This has been rectified last week, fortunately, so this shouldn't happen again. I re-enabled mail for all accounts having been disabled due to bounces. Looks like I am receiving mail again! Thank you, Kyle Marek -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Mailing list subscription problems
On Dec 19 12:50, David Standish via Cygwin wrote: > On 12/19/22, Kyle Marek via Cygwin wrote: > > (CC'd the public mailing list for visibility of problems that may be > > affecting others) > > > > Hello, > > > > Today I received an email from cygwin-boun...@cygwin.com with the > > subject line of "You have been unsubscribed from the Cygwin mailing > > list". I also just noticed that my Cygwin directory doesn't have any > > emails since the email identified by the following headers: > > [...] > > I've experienced the same problem. I reactivated my subscription a > couple times. > > More cygwin mail has been getting through to me that last few days. > Hopefully google has relaxed their filtering, Actually, Google hasn't relaxed their filtering, rather the DNS record of the cygwin.com domain was the culprit. It didn't have the required (by Google) DKIM/SFP records. This has been rectified last week, fortunately, so this shouldn't happen again. I re-enabled mail for all accounts having been disabled due to bounces. HTH, Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Mailing list subscription problems
ditto! On Mon, Dec 19, 2022 at 9:51 AM David Standish via Cygwin wrote: > On 12/19/22, Kyle Marek via Cygwin wrote: > > (CC'd the public mailing list for visibility of problems that may be > > affecting others) > > > > Hello, > > > > Today I received an email from cygwin-boun...@cygwin.com with the > > subject line of "You have been unsubscribed from the Cygwin mailing > > list". I also just noticed that my Cygwin directory doesn't have any > > emails since the email identified by the following headers: > > > > Date: Thu, 24 Nov 2022 00:42:07 -0800 > > Message-ID: > > Subject: You have been added to Newcommercial08 > > From: Newcommercial08 > > To: cygwin@cygwin.com > > > > I'm pretty sure the from address is so bounces are returned to an > > address that monitors for bounces. I am guessing that Google has been > > bouncing emails from the Cygwin mailing servers, and mailman > > automatically unsubscribed me after 25 days of not being able to deliver > > a single email to me. However, I am still receiving emails from mailman > > itself. > > > > I re-subscribed, logged into the mailman web interface, and confirming > > that I am re-subscribed as of 02:47 UTC. I can see on the online archive > > that the mailing list has received emails since then, but I am still not > > receiving them. Note that they are NOT being sent to my spam directory. > > > > So... Are the mailing list emails being bounced by Google? > > > > Thank you, > > Kyle Marek > > > > -- > > Problem reports: https://cygwin.com/problems.html > > FAQ: https://cygwin.com/faq/ > > Documentation:https://cygwin.com/docs.html > > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple > > > > I've experienced the same problem. I reactivated my subscription a > couple times. > > More cygwin mail has been getting through to me that last few days. > Hopefully google has relaxed their filtering, > > David > > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation:https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple > -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Mailing list subscription problems
On 12/19/22, Kyle Marek via Cygwin wrote: > (CC'd the public mailing list for visibility of problems that may be > affecting others) > > Hello, > > Today I received an email from cygwin-boun...@cygwin.com with the > subject line of "You have been unsubscribed from the Cygwin mailing > list". I also just noticed that my Cygwin directory doesn't have any > emails since the email identified by the following headers: > > Date: Thu, 24 Nov 2022 00:42:07 -0800 > Message-ID: > Subject: You have been added to Newcommercial08 > From: Newcommercial08 > To: cygwin@cygwin.com > > I'm pretty sure the from address is so bounces are returned to an > address that monitors for bounces. I am guessing that Google has been > bouncing emails from the Cygwin mailing servers, and mailman > automatically unsubscribed me after 25 days of not being able to deliver > a single email to me. However, I am still receiving emails from mailman > itself. > > I re-subscribed, logged into the mailman web interface, and confirming > that I am re-subscribed as of 02:47 UTC. I can see on the online archive > that the mailing list has received emails since then, but I am still not > receiving them. Note that they are NOT being sent to my spam directory. > > So... Are the mailing list emails being bounced by Google? > > Thank you, > Kyle Marek > > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation:https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple > I've experienced the same problem. I reactivated my subscription a couple times. More cygwin mail has been getting through to me that last few days. Hopefully google has relaxed their filtering, David -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Xlib: sequence lost (0x10000 > 0x21c) in reply type 0x13!
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 (0x1 > 0x16c) in reply type 0x13! Xlib: sequence lost (0x1 > 0x172) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x17f) in reply type 0xf! Xlib: sequence lost (0x1 > 0x185) in reply type 0x1c! Xlib: sequence lost (0x1 > 0x1ba) in reply type 0xf! Xlib: sequence lost (0x1 > 0x519) in reply type 0xf! Did something go awry with the update? -- Jim Reisert AD1C, , https://ad1c.us -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Mailing list subscription problems
(CC'd the public mailing list for visibility of problems that may be affecting others) Hello, Today I received an email from cygwin-boun...@cygwin.com with the subject line of "You have been unsubscribed from the Cygwin mailing list". I also just noticed that my Cygwin directory doesn't have any emails since the email identified by the following headers: Date: Thu, 24 Nov 2022 00:42:07 -0800 Message-ID: Subject: You have been added to Newcommercial08 From: Newcommercial08 To: cygwin@cygwin.com I'm pretty sure the from address is so bounces are returned to an address that monitors for bounces. I am guessing that Google has been bouncing emails from the Cygwin mailing servers, and mailman automatically unsubscribed me after 25 days of not being able to deliver a single email to me. However, I am still receiving emails from mailman itself. I re-subscribed, logged into the mailman web interface, and confirming that I am re-subscribed as of 02:47 UTC. I can see on the online archive that the mailing list has received emails since then, but I am still not receiving them. Note that they are NOT being sent to my spam directory. So... Are the mailing list emails being bounced by Google? Thank you, Kyle Marek -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: gcc v.11.3.0 failing - possible cause gcc or libreadline.a?
>>> In a gcc build script terminating with the instruction
>>> gcc -w -static -o myexe -O3 ./myarchive.a -lreadline -lncurses -lm
>>> I have suddenly started getting very many instances of both of
>>> ld: /usr/src/debug/readline-8.2-2/terminal.c:nn various: undefined
>>> reference to `{various}'
>>> ld: /usr/src/debug/readline-8.2-2/display.c:nn various: undefined
>>> reference to `{various}'
>>> and the build fails.
>> The problem was with readline not gcc
>> and I assume originates in myarchive.a and the required switch -lreadline in
>> the gcc line
>> rather than in readline: nevertheless I reverted both libreadline-devel and
>> libreadline7
>> from 8.2-2 to 7.03 and the problem went away.
> Please provide a few examples which include the actual texts of "nn various"
> and
> `{various}' especially where any prefixes vary.
> Did you also upgrade/downgrade libncurses-devel concurrent with
> libreadline-devel as they are dependent?
> Why suppress all warnings -w from the ld (or any) phase of compilation?
> Those warnings could tell you what causes an issue.
No I didn't upgrade / downgrade libncurses-devel concurrently with
libreadline-devel.
In fact after upgrading back to 8.2-2 and confirming the failed build I
retained all current and up-to-date
and made _just_one_change_: I extracted the single file libreadline.a from
libreadline-devel-8.1-2.tar.xz
(i.e. just one reversion to 8.1 not two to 7.0) and substituted it in place
leaving everything else as for 8.2-2
including libreadline.dll.a and confirmed that this single substitution allowed
the build.
I suppress the warnings because there are so many of them! I can supply them
but for the moment the issues
that prevent a successful build using libreadline.a (8.2-2) are listed in the
attached text file.
Thank you very much for taking an interest.
Description:
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Fork issues with 3.4 in Docker only
On Dec 18 10:18, Christoph Reiter via Cygwin wrote: > After the upgrade to 3.4 (disclaimer: in MSYS2) I'm seeing, and getting > reports > of, various things failing in Docker only, for example: > > 1 [main] pacman 252 child_copy: dll data read copy failed, > 0x7FF8C816C000..0x7FF8C8178EB0, done 0, windows pid 5096, Win32 error > 299 > 0 [main] pacman 251 dofork: child -1 - forked process 5096 died > unexpectedly, retry 0, exit code 0xC005, errno 11 > 0 [main] pacman 253 child_copy: dll data read copy failed, > 0x7FF8C816C000..0x7FF8C8178EB0, done 0, windows pid 584, Win32 error > 299 > 67887 [main] pacman 251 dofork: child -1 - forked process 584 died > unexpectedly, retry 0, exit code 0xC005, errno 11 > 0 [main] pacman 254 child_copy: dll data read copy failed, > 0x7FF8C816C000..0x7FF8C8178EB0, done 0, windows pid 2336, Win32 error > 299 > 124719 [main] pacman 251 dofork: child -1 - forked process 2336 died > unexpectedly, retry 0, exit code 0xC005, errno 11 > > Reverting > https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=943433b00cacdde0cb9507d0178770a2fb67bd71 > fixes things again. > > Note that this doesn't happen outside of Docker, I've built more than 100 > packages with 3.4 on different hosts without any issues, and the errors in > Docker are pretty consistent, so I'm guessing that something with ASLR behaves > differently under Docker(?) No idea what docker is doing differently, but you could try to switch off ASLR for the Cygwin DLL. Right now, starting with 3.4.0, it's supposed to be the only DLL using ASLR by default in the Cygwin distro, all other DLLs should still use fixed addresses. Try this: cp /bin/cygwin1.dll ~/docker-cygwin1.dll peflags -d0 ~/docker-cygwin1.dll Then copy that DLL over to /bin/cygwin1.dll in your docker image and try again. Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
