From: Jon Turney <jon.turney@dronecode.org.uk>
To: Ken Whitesell <KenWhitesell@comcast.net>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified
Date: Wed, 19 Jan 2022 19:28:57 +0000 [thread overview]
Message-ID: <4f4d8d34-3e30-82fe-4be2-2926da2c1c6a@dronecode.org.uk> (raw)
In-Reply-To: <02b8ba82-0a40-e9ea-c4e6-fe201097d957@comcast.net>
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])
You might find that starting the server and specifying a fixed dpi value
with the '-dpi' option might workaround this.
[1] https://cygwin.com/pipermail/cygwin-announce/2021-November/010286.html
> 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.
(This is presumably somehow related to the fact that we now keep that
window at the same pixel dimensions, rather than allowing Windows to
scale it).
next prev parent reply other threads:[~2022-01-19 19:29 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 [this message]
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 ` Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified - "Solution" found Ken Whitesell
2022-02-05 14:25 ` 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:
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=4f4d8d34-3e30-82fe-4be2-2926da2c1c6a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=KenWhitesell@comcast.net \
--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).