Actually, I found a way to make it work somehow, namely by passing "-engine
1" to XWin.exe, following a (21 year old) tip from here:
https://cygwin-xfree.cygwin.narkive.com/maSzrlKY/crash-when-remote-desktop-changes-screen-resolutions
ons. 19. feb. 2025 kl. 19:59 skrev Erik Dybdahl <erik...@gmail.com>:
> Thanks,
> That first command does indeed cause a server window titled "Cygwin/X:0.0
> to appear (an all white window).
> The next command gives some info and warnings, and then 10 of these:
>
> winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 88760827
> winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum (10)
> reached. No more failure messages will be printed.
>
> and nothing shows up.
>
>
>
> tir. 18. feb. 2025 kl. 20:04 skrev Jon Turney <jon.tur...@dronecode.org.uk
> >:
>
>> On 18/02/2025 14:56, Erik Dybdahl via Cygwin wrote:
>> > 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.
>>
>> Perhaps you could try the simplest possible way of running things as a
>> test:
>>
>> XWin :0 &
>> DISPLAY=:0.0 xterm
>>
>> If I understand correctly, this gives you a server window (titled
>> "Cygwin/X:0.0"), but no xterm window inside it.
>>
>> If the xterm client can't connect to the server, this might be due to a
>> interference from some firewall software (as the Cygwin UNIX domain
>> socket used here is emulated by Cygwin using a loopback TCP/IP socket).
>>
>>
--
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
