DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 51IF0i3q3506866 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 51IF0i3q3506866 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=i+uumgpP X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8911D3858404 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1739890843; bh=YdBdgplxfT+vK1NQswSs68tSZDiy1eh2JwpnNO5J34I=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=i+uumgpPfUrB5+IoZ59UlKSgiHvhlibUXppRVg3oK2aiDs2ZFYT7MQEdqPnyDqgJa 6uS5jE/OtWgQ7/Nzk5iyMTS/pFsuVa5okqDeGFUsCuQ+7TV92jg02mvH6q04pLHQEN U87DtrRB7n2wU7MsQW5B2EgMRZr4NfZVxwUiklkw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 65E5F3858C50 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 65E5F3858C50 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1739890588; cv=none; b=Aku53T0fLmIwKVlCkzTkTiRch3u7HNswdvGOu3ftUeF8bkd8MWHXfFPVsGrF6f0wHZXXKLc1dmBeZn5RJaEmyeFv4QADvzpk7UWfiJ/nvKw9wo27gNP9A7F6U/iTrrGnAo5DQb+WvFxb5zmcrqYCANUaMu+s7Ps43JYKtn6UMtA= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1739890588; c=relaxed/simple; bh=yaAiojtNSmHk9V9qj+0QCofdfVwoBUxqxTpgSYMv+S8=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=pUNMsqKLY31aN4zbyzBIRDkP3WsXqSMOfmOeT/ytE0qUzBb21kAIqMBmGCQbHN3ReBcAKzFeEZJLYR6agaIwL6a0fgmhtCGms7JJeUOSAtE5DdcyEVz234ou8u9L8kSmUmkr+A0RhqH4FWjtiYNE/J66xaDpVxEUk4TC4ZkqI/Q= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 65E5F3858C50 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739890587; x=1740495387; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BZWzjU2ux0ZlNehof8qtRnM0i0XFqvJbpk0lyQNqvwU=; b=dkjd8fx5sAPgt7jWArI2LEjAAI5bOUEebnFohx0qX4lD23UYQOH/XrVDTu28TzfWmr JEDbpzg8GP9+YU9PuD74hw9o5dBDC0uxWOtETCHhHSm2BAmdx7Hbvm7yNJwx29A/lXAf ywreisXeUc1E72S337w+AeKIhrwzwSyGsTjHgJDLmQdwR2jiN5mVOyZF41zDJxFVoE5p I0/8sDygYBCufomrJzzeDrHghwNliBJVctKGVM31BLno7TO0eyxnHAPv7PbL0bdDQK3l d8SY0R1b2IP6aWCQxl/tXu/TYSBc/20W58dpzKzkR+AGQXDqHnCiQ6oN1Nr1n2/u+qhy Avfg== X-Gm-Message-State: AOJu0YwEgUwwgN24LPeSntwqutD3g5T6jR7sONEbKClvK6GzndtuKsVE 5pQSzj84WipFB+P0j9PylDtdwew7Jx2idK4KvbNwsCogz2pvG5lksWSD5q9WnH/uUkCE0wRlGO4 BpIesd0mQcL+Yu+CiBbWATAHZnm1mOJ2q X-Gm-Gg: ASbGncuba2Oq2LIZla1PU7jZaAU8fK/7d1AeqKhrlFrtfXnsqQihuqv1MlFiaHo56UR 0htC91utgENjksQcl782R2S+33AVP0jDxCSTRFqA0pqqGpcC8GHyEhhH980C7zWcoM6ov2je6/6 g= X-Google-Smtp-Source: AGHT+IH8ZUSYrwDpMLHNbcVto1AZ0kK7rimKZN92G0EIvijyQfEj8vrIMNPrckmQOOuz1n03/fsVraqcQbNZoYlH3vY= X-Received: by 2002:a17:90a:e70b:b0:2ee:9661:eafb with SMTP id 98e67ed59e1d1-2fcb4d6983fmr3537a91.12.1739890587104; Tue, 18 Feb 2025 06:56:27 -0800 (PST) MIME-Version: 1.0 Date: Tue, 18 Feb 2025 15:56:01 +0100 X-Gm-Features: AWEUYZngulqB8KSNwgLaJ3S9BHRbQZObV-SReEArOiJnIDeqHwBVZYtEQJo37uM Message-ID: Subject: Cygwin/X not working under Windows 11 To: cygwin AT cygwin DOT com X-Content-Filtered-By: Mailman/MimeDel 2.1.30 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Erik Dybdahl via Cygwin Reply-To: Erik Dybdahl Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" Hi, I have been using Cygwin for the last twenty years, and fifteen years ago a colleague of mine introduced me to Cygwin/X. I've used it ever since, because it's much better to have Xterm windows controlled by this than to have a number of mintty instances started under and controlled by MS Windows. Sadly, after switching to a new laptop running Windows 11, it does not work anymore. This is the bin/X.sh script I've been using: #!/bin/sh export DISPLAY=":0.0" export XENVIRONMENT="${HOME}/.Xresources" XWin -clipboard -dpi 200 & sleep 5 echo "Starting wmaker..." wmaker & wait and here is how it was started: C:\cygwin64\bin\mintty.exe /bin/bash -l -e c:\cygwin64\home\dybdaeri\bin\X.sh This starts XWin.exe, with a few Xterm windows in it. Now, on my new laptop, only a blank screen is shown, and I am not able to get any xterm window presented there. The documentation says the script startxwin should be used, and I have tried it, and it does start an XWin.exe process, but nothing is shown, not even a blank screen. There is a lot of information shown during startup, but that's also the case on my old laptop where this is working, so hard to say from that what the problem might be. I've also tried the startx script, to no avail. Please note that I am not using Cygwin/X to to start GUIs on remote servers, it's solely a tool I use for avoiding having to revert to having MS Window control the Cygwin terminals I start. (I use xterm, with different fonts and sizes for different purposes.) If anybody here is able to guide me on this, I would be most grateful. Thanks, Erik -- 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