From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-c1p-023461.sys.comcast.net (resqmta-c1p-023461.sys.comcast.net [IPv6:2001:558:fd00:56::a]) by sourceware.org (Postfix) with ESMTPS id 767C33858409 for ; Wed, 19 Jan 2022 00:02:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 767C33858409 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=comcast.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=comcast.net Received: from resomta-c1p-022589.sys.comcast.net ([96.102.18.236]) by resqmta-c1p-023461.sys.comcast.net with ESMTP id 9qXwn7dlkG5Fo9yQZnYFew; Wed, 19 Jan 2022 00:02:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1642550535; bh=DZPb7N6V+JjJTwpFjoPI4h1uW/SsBo4/93udBMGqoP0=; h=Received:Received:Message-ID:Date:MIME-Version:Subject:From:To: Content-Type; b=TeAXO6sI6/fB/L/1LPRsA1YcZY0xRo2b3+OAgJHrWh/IBNtXkywAIa9JyQ3TaL56O bXBMg+UtcbzVihQTwj+8wpB62kNJPrQNtKjGbzDW0QegasNSY+b0xBGa+XnSxzVJ+Y xyolStE9M4tl/kUvMDJFkZk24gULFqqAma8uzdfBmWnFQxJeUEOtW9AIFsRpAt4eZm EF6PYKDYkt1VuhT6wkxWQO40TkrzHrXsaFpRQ03ld5J3Lc7ovw49SYAZos1RuHRs1U SF9KDrFm92mk/GiUZ2PJCF+ZSqOubRDNp90Nc/mQLZY5qHJ5+87tUQhArVziC29Zb6 bd1fqP828wvAg== Received: from [IPV6:2601:541:c103:bf60:5016:eaab:4a09:5a0] ([IPv6:2601:541:c103:bf60:5016:eaab:4a09:5a0]) by resomta-c1p-022589.sys.comcast.net with ESMTPSA id 9yQXnP1sCIna69yQYnjLvG; Wed, 19 Jan 2022 00:02:15 +0000 X-Xfinity-VMeta: sc=0.00;st=legit Message-ID: <02b8ba82-0a40-e9ea-c4e6-fe201097d957@comcast.net> Date: Tue, 18 Jan 2022 19:02:14 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Cygwin/X with Win10 display scaling corrupting font display of typed characters - Issue identified Content-Language: en-US From: Ken Whitesell To: cygwin@cygwin.com References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, JMQ_SPF_NEUTRAL, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2022 00:02:17 -0000 On 1/17/2022 1:29 PM, Ken Whitesell wrote: > Problem: When moving an XTerm window from the primary display to the > second monitor, characters typed into that window are "clipped" at the > top. Only about the bottom 75% is drawn. No lower-case letters taller > than the "half-height" letters render properly. (Letters such as "a", > "c", "m", "n", etc are all rendered correctly. All capital letters and > tall lower-case letters (e.g. "b" and "d") have the top quarter > clipped off. Additionally the XTerm window shows thin black bars on > the right side of the window and along the bottom of the window. > > The bash prompt and most all characters displayed as the result of the > output of a command all display correctly - this is *primarily* > affecting characters being typed, and before the "enter" key is > pressed. (There is one special case regarding displayed characters. If > a program is creating a full screen of output, such as "man", the top > line of the screen is clipped.) > > If the window is in the primary display when the characters are typed, > and then the window is moved to the second monitor, the > previously-typed characters remain correctly formed, and only new > characters typed while the window is in the second monitor are clipped. > > Environment: The primary display is the laptop's built-in display > (1920x1080, 17"). The second monitor is a 27" also at 1920x1080. > Operating system is Windows 10, with all current patches and updates. > (Ver reports Microsoft Windows [Version 10.0.19044.1466]). XWin server > is being started with this command line: > > E:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec > /usr/bin/startxwin -- -listen tcp" > > Additional info: This appears to be related to using the display > "Scaling" option, where the laptop's display is set at 125% and the > external monitor's display is set at 100%. If I set both displays the > same - either both at 100% _or_ both at 125%, the problem does not > appear. > > 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. > > Note: XTerm is _not_ the only program that exhibits this behavior. > This is consistent among all applications tried, including geany, > hexedit, mate-terminal, and lxterminal. (The visual behavior is > slightly different for "full screen" application such as geany and > hexedit, but it's still apparent that some clipping is occurring with > characters being typed.) > > Other version information: Cygwin setup version 2.915, packages > showing as up-to-date include xterm 370-1, xinit 1.4.1-1, xorg-server > 21.1.3-1, xorg-x11-fonts-* 7.5-4. (Unsure what other information may > be useful.) > > I've tried searching the message archives, going back through 2018 and > have not seen anything that appears relevant. Other searches haven't > proved useful, other than indicating that I should try applications > other than XTerm. > > I have tried various settings in different locations, including > specifying "-resize=none" and/or -screen options for both monitors. > > No changes have been made to system.XWinrc. > > /etc/X11/xinit/startxwinrc has the following lines added before the > line "exec /usr/bin/xwin-xdg-menu" line at the bottom of the file: > >     /bin/xterm -fa 'DejaVu Sans Mono' -fs 12 -geometry 100x33 & >     /bin/xterm -fa 'DejaVu Sans Mono' -fs 12 -geometry 100x33 & >     /bin/xterm -fa 'DejaVu Sans Mono' -fs 12 -geometry 100x33 & >     /bin/xterm -fa 'DejaVu Sans Mono' -fs 12 -geometry 100x33 & > > There is no .startxwinrc file in $HOME. > > I will gladly provide any additional information that may help. > > Is there a known solution for this? (Or is it known that there is no > solution?) > > 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.