From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from re-prd-fep-049.btinternet.com (mailomta27-re.btinternet.com [213.120.69.120]) by sourceware.org (Postfix) with ESMTPS id C29023858D39 for ; Tue, 26 Oct 2021 15:03:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C29023858D39 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dronecode.org.uk Received: from re-prd-rgout-001.btmx-prd.synchronoss.net ([10.2.54.4]) by re-prd-fep-049.btinternet.com with ESMTP id <20211026150327.FZCH8938.re-prd-fep-049.btinternet.com@re-prd-rgout-001.btmx-prd.synchronoss.net>; Tue, 26 Oct 2021 16:03:27 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com; bimi=skipped X-SNCR-Rigid: 613A8CC3068D9FE8 X-Originating-IP: [81.129.146.209] X-OWM-Source-IP: 81.129.146.209 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvtddrvdefkedgheehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpedvtdetffekveevjeegheeglefhtdeggfeilefggfdutedufedvgefgieeiffdtveenucfkphepkedurdduvdelrddugeeirddvtdelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddutdefngdpihhnvghtpeekuddruddvledrudegiedrvddtledpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomhdprhgtphhtthhopehmohhsshestghsrdhumhgrshhsrdgvughu X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.103] (81.129.146.209) by re-prd-rgout-001.btmx-prd.synchronoss.net (5.8.716.04) (authenticated as jonturney@btinternet.com) id 613A8CC3068D9FE8; Tue, 26 Oct 2021 16:03:27 +0100 Message-ID: Date: Tue, 26 Oct 2021 16:02:35 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: Confusing Cygwin X / xlaunch issue Content-Language: en-GB To: moss@cs.umass.edu, The Cygwin Mailing List References: <1e4edecf-166c-e3c1-f961-b31bfa01271f@cs.umass.edu> From: Jon Turney In-Reply-To: <1e4edecf-166c-e3c1-f961-b31bfa01271f@cs.umass.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1191.2 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_NONE, 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: Tue, 26 Oct 2021 15:03:30 -0000 On 24/10/2021 12:01, Eliot Moss wrote: > First, things work fine when I am using just my hi-res laptop display, > or that > display plus a hi-res external display in "Extend these displays" mode > according to Windows 10.  At present I am using a lower resolution external > display (becaue I am on an extended trip and it's what I have) in "Extend > these displays" mode with my hi-res laptop display.  This seems to > confuse X > (and also xlaunch?).  Here are the issues: Thanks for reporting this problem. > When booted with the external lo-res display as the main display: > > - xterm windows come up with a very large font. > - The X menu (controlled by .XWinrc) does not come up. This means that you're right-clicking on the notification area icon, but no menu appears? If so, I guess this means that we're getting confused about where to place the menu, but I'm not sure how that could happen. [...] > It seems that, at the least, I need to *start* X when the laptop (hi-res) > display is main.  I'm less clear as to whether I need to *boot* with it > main > (I can try that later). > > Is there an explanation for this?  Should I be doing something differently? > Is there a bug?  Thanks for any insight you can offer!  Eliot Moss 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. > winInitializeScreenDefaults - primary monitor w 3240 h 2160 > winInitializeScreenDefaults - native DPI x 192 y 192 [...] > [ 1035.750] winWindowProc - WM_DISPLAYCHANGE - new width: 2560 new height: 2048 new bpp: 32 As a workaround, you might experiment with using the xserver option '-dpi' to set a value corresponding to your hi-res display, so that will be used even if the normal-res display is Windows' primary monitor.