X windows fatal errors following install of Feature update to Windows 10, version 1803

[Jeff Rankin]

Hi All,

 

On two Windows 10/Cygwin installations, I have fatal errors with X windows following installation of “Feature update to Windows 10, version 1803” yesterday (May 1). The startxwin command output tail is:

 

waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.

winClipboardProc - XDestroyWindow succeeded.

winMultiWindowXMsgProc - Fatal error 1 on xcb connection

winDeinitMultiWindowWM - Noting shutdown in progress

(II) Server terminated successfully (0). Closing log file.

 

An xwin stackdump is produced:

 

jrankin@Windows10: ~ cat xwin-xdg-menu.exe.stackdump

Exception: STATUS_ACCESS_VIOLATION at eip=6BB0F8F0

eax=201DE7C8 ebx=00010007 ecx=00000002 edx=0000FFFF esi=00000000 edi=201DE7F0

ebp=201D2950 esp=0067B550 program=C:\cygwin\bin\xwin-xdg-menu.exe, pid 3720, thread main

cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B

Stack trace:

Frame     Function  Args

201D2950  6BB0F8F0 (00000919, 000F0000, 00000344, 201DCA00)

 

I can start x using the startx command (it starts twm) but many clients, including xclock and eog don’t run and output stackdump files. Some clients do run, e.g. xload. I followed instructions here (https://x.cygwin.com/devel/backtrace.html), installed xorg-server-cygwin-crashreporter, and reproduced the crash, but I don’t know where the crashreporter puts it output – there’s nothing in the log directory. Let me know if I can provide additional information.

 

Thank you - Jeff


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple