public inbox for
 help / color / mirror / Atom feed
From: Ken Whitesell <>
To: The Cygwin Mailing List <>
Subject: Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified - "Solution" found
Date: Wed, 26 Jan 2022 22:12:58 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Thank You!!!

On 1/24/2022 10:02 AM, Jon Turney wrote:
> 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:
> [...]
>>>> 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?

Yes, the laptop display is the primary monitor in all cases.

But, the real reason for my reply at this point is to report that I have 
found a solution for _my_ issue.

I make no guarantees about any problems anyone else may be facing, nor 
can I make any statement about whether or not this causes other problems.

Obligatory disclaimer: I don't really know what I'm doing here. I'm not 
a Windows developer, and I know just enough about cygwin to muddle my 
way through doing what I want to do with the help of the mailing lists 
and other resources. I'm not in a position to _explain_ anything. This 
works for me, but that's as far as I can go.

First, the bottom line:

XWin.exe.manifest, line 21


Some details:

I managed to get to a point where I could build the packages from source 
and install them. I looked at the commit you referred me to, and started 
reverting changes, one-by-one - at least in so far as the change 
appeared to make sense to me.

Anyway, I got to this change, and sure enough, it worked. Removing the 
"PerMonitorV2" solved the issue. Also, I confirmed that it's the 
"PerMonitorV2" that is causing the issue and not having both of them by 
running another test with just the "PerMonitorV2" - and that still shows 
the problem.

References with further information if it's going to be helpful to 

  reply	other threads:[~2022-01-27  3:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 18:29 Cygwin/X with Win10 display scaling corrupting font display of typed characters Ken Whitesell
2022-01-19  0:02 ` Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified Ken Whitesell
2022-01-19 19:28   ` Jon Turney
2022-01-20  1:01     ` Ken Whitesell
2022-01-21 18:26       ` Cygwin/X with Win[10]-^ display scaling corrupting font display of typed characters - Issue [identified]-???? L A Walsh
2022-01-23 20:25         ` Cygwin/X display scaling corrupting font display of typed characters; L A Walsh
2022-01-24 15:02       ` Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified Jon Turney
2022-01-27  3:12         ` Ken Whitesell [this message]
2022-02-05 14:25           ` Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified - "Solution" found Jon Turney
2022-08-14 11:08             ` Jon Turney

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).