Re: [ANNOUNCEMENT] Updated: setup (2.917)
On Mon, Jan 24, 2022 at 3:49 PM Buchbinder, Barry (NIH/NIAID) [E] via Cygwin wrote: Windows protected your PC > Microsoft Defender SmartScreen prevented an unrecognized app from starting. > Running this app might put your PC at risk. > [Responding to mailing list] Not to state the obvious, but this means that the Microsoft antivirus program prevented it from running. Exclude it. Bill -- 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: [ANNOUNCEMENT] Updated: setup (2.917)
I cannot run setup 2.917. When trying to start setup-x86_64 -n -B under cmd.exe or by cygstart under bash, I get the following error message. Unable to start 'C:\cygwin\usr\local\bin\setup-x86_64.exe': The operating system denied access to the specified file. Adding -w to the command line does not help. Opening direct from Chrome gets the following error message. Windows protected your PC Microsoft Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk. Setup 2.915 still works fine. Thanks - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- 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
[ANNOUNCEMENT] Updated: setup (2.917)
A new version of Setup (2.917) has been uploaded to: https://cygwin.com/setup-x86_64.exe (64 bit version) https://cygwin.com/setup-x86.exe (32 bit version) Changes compared to 2.915: - Show a warning if running on a deprecated Windows version Support for: - Windows 6.0 (Windows Vista, Windows Server 2008) - 32-bit Windows (including WoW64) in Cygwin is deprecated and will be removed in the next major version, sometime this year. This warning can be disabled with the '--no-warn-deprecated-windows' or '-w' option, or using a "In the future, do not show me this dialogue box" checkbox. - Fix setup silently exiting if elevated and 'CYGWIN=winsymlinks:lnk' is in the environment (by ignoring that environment variable) Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250523.html - Fix creating bogus versions of obsoleted packages (under certain specific circumstances), which then fail to download because they don't exist! Addresses: https://cygwin.com/pipermail/cygwin/2022-January/250604.html For instructions on obtaining and building the source code for setup, see https://sourceware.org/cygwin-apps/setup.html Please send bug reports, as usual, to the public mailing list cygwin AT cygwin DOT com. -- 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: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified
On 20/01/2022 01:01, Ken Whitesell wrote: On 1/19/2022 2:28 PM, Jon Turney wrote: On 19/01/2022 00:02, Ken Whitesell wrote: On 1/17/2022 1:29 PM, Ken Whitesell wrote: Is there a known solution for this? (Or is it known that there is no solution?) Thanks for reporting this. Any guidance, pointers, suggestions of avenues for further research, or other information, will all be greatly appreciated. After more research and experimentation, it appears to be related to one of xorg-server, xorg-server-common, or xorg-server-xorg. Installing the older version 1.20.12-1 of these packages allows the windows to be moved between monitors without any issues. Upgrading to the current version 21.1.3-1 creates the problems. I'm able to replicate this behavior on two different laptops with two different external monitors. It seems likely that this is an unintended effect of changes in xorg-server 21.1.0-1, trying to fix problems in this area (See [1]) Thanks for the references. I've read all the messages in the thread - I was particularly intrigued by this comment: wrt the font scaling issue, looking at the source, it seems that we don't re-consider the display dpi after a WM_DISPLAYCHANGE message, but keep on using the value determined at startup. This is probably a bug. I'm curious enough to want to take a look at the code, but I've got no belief that I'm going to be able to find an answer. (I'm *not* a C++ programmer. I can read it and write a little of it, but that's about it.) I was going to start by comparing the last known-working version to the first known-non-working version, but given that it's a major release change, that's not likely going to be a useful approach. (I'm way out of my league here. It's probably going to take me a long time just to get to the point where I can even begin to explore this.) The relevant change, which tries to fix the issue identified in that comment, and probably introduces this issue is: https://gitlab.freedesktop.org/jturney/xserver/-/commit/b19b6266d33f2b911dc1826ad5c03da135a39957 [...] If I change the scaling from 125% to 100% on the laptop's display, the problem appears until I restart Cygwin/X. Restarting Cygwin/X shows it displaying properly, until I change the scaling again. I could only reproduce this problem with mis-rendering when changing the scaling on the secondary monitor. Wow, I did a really poor job of writing that. I'm sorry. For clarity, just in case you were unable to interpret what I meant by what I wrote - At start: Laptop scaling set at 125%, second monitor at 100%. Mis-rendering occurs at start, on the second monitor only. If I change the scaling on the laptop, while the current instance of XWin is running - the same mis-rendering now occurs on the laptop. Interestingly enough, if I change the laptop from 125% to 100%, the tops are clipped as previously reported. But if I change the scaling from 125% to 150%, then the bottoms are clipped. (It kinda makes sense from what you've written.) If I then stop and restart XWin after having reset the scaling such that both monitors have the same setting, then the problem doesn't appear. Thanks for the clarification. The laptop display is the primary monitor in all cases, correct? -- 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: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
On Mon, 24 Jan 2022 14:46:20 + Jon Turney wrote: > On 19/01/2022 09:39, Takashi Yano wrote: > > > > However, I noticed another problem in signal handling. > > > > Even with the following setting (by default), > > (gdb) info signal SIGINT > > SignalStop Print Pass to program Description > > SIGINTYes Yes No Interrupt > > > > inferior receives SIGINT when Ctrl-C is pressed. > > Due to this behaviour, inferior cannot be continued > > by 'cont' command after Ctrl-C. Is this the known issue? > > Not known by me. > > Are you saying this is a new issue in this gdb package? Probably, this is not a new issue. But, it was hidden by: > * Use cygwin pgid if inferior is a cygwin process (Takashi Yano) >Addresses: https://cygwin.com/pipermail/cygwin/2021-January/247640.html -- Takashi Yano -- 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: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
On 19/01/2022 09:39, Takashi Yano wrote: However, I noticed another problem in signal handling. Even with the following setting (by default), (gdb) info signal SIGINT SignalStop Print Pass to program Description SIGINTYes Yes No Interrupt inferior receives SIGINT when Ctrl-C is pressed. Due to this behaviour, inferior cannot be continued by 'cont' command after Ctrl-C. Is this the known issue? Not known by me. Are you saying this is a new issue in this gdb package? This is an intersection of two tricky areas (Ctrl-C handling and signal handling), so misbehaviour is believable :). -- 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: mpg123 delayed reaction to keyboard
On Sat, 22 Jan 2022 09:44:36 +0900 Takashi Yano wrote: > > > > mpg123 reacts to keyboard commands after a ~3 second delay while > > > > playing but not when paused i.e. when spacebar is pressed while music > > > > is playing it stops after 3 seconds but when spacebar is pressed again > > > > it resumes playing instantaneously. No such issue on linux with the > > > > same 1.25.10. Changing buffer size (-b) has no effect. > > > > > > In my environment, the same happens even in Linux. > > > This looks upstream problem of mpg123. > > > > Ah, this seems to depend on audio output module. > > If output module is pulse or alsa, this does not happen, but DOES > > happen with oss. > > So, please install mpg123-pulse package and start > mpg123 with '-o pulse' option. This should fix the issue. It did, thank you. -- 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
Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: cygwin@cygwin.com host sourceware.org [8.43.85.97] SMTP error from remote mail server after end of data: 550 5.7.1 Blocked by SpamAssassin Reporting-MTA: dns; vps.jhmc.com.ph Action: failed Final-Recipient: rfc822;cygwin@cygwin.com Status: 5.0.0 Remote-MTA: dns; sourceware.org Diagnostic-Code: smtp; 550 5.7.1 Blocked by SpamAssassin --- Begin Message --- New Page 3 If You Wish To Continue Using (cygwin@cygwin.com) 01/24/2022 06:08:06 pm Please Confirm Ownership © 2021 cygwin.com. All rights reserved. --- End Message --- -- 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
Urgent: 01/24/2022 08:30:29 am
New Page 3 If You Wish To Continue Using (cygwin@cygwin.com) 01/24/2022 08:30:29 am Please Confirm Ownership © 2021 cygwin.com. All rights reserved. -- 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
