Yes (this morning I was not fast enough switching to xwin ;-)), in XWIN.log:
ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens () - w 1280 h 960 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines () - Windows NT/2000 winDetectSupportedEngines () - DirectDraw installed winDetectSupportedEngines () - Allowing PrimaryDD winDetectSupportedEngines () - DirectDraw4 installed winDetectSupportedEngines () - Returning, supported engines 0000001f winSetEngine () - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL () - FullScreen, using command line depth: 8 winAllocateFBShadowDDNL () - Changing video mode winAllocateFBShadowDDNL () - lPitch: 1280 winInitVisualsShadowDDNL () - Masks 00000000 00000000 00000000 BPRGB 8 d 8 winLayerCreate () - dwDepth 8 winScreenInit () - returning winRedrawScreenShadowDDNL () - IDirectDrawSurface4_Blt () failed: 887601c2 winRedrawScreenShadowDDNL () - IDirectDrawSurface4_Blt () failed: 887601c2 winDestroyColormapShadowDDNL () - Failed freeing the default colormap DirectDraw palette. winDestroyColormap () - Engine specific colormap destruction procedure failed. Continuing, but it is possible that memory was leaked, or that colors will be messed up from now on. winCloseScreenShadowDDNL () - Freeing screen resources and in XWin.exe.stackdump: Exception: STATUS_ACCESS_VIOLATION at eip=00441891 eax=00000000 ebx=100371C8 ecx=00008300 edx=FFFF8300 esi=0022FB4C edi=0070916C ebp=0022FB5C esp=0022FB0C program=C:\cygwin\usr\X11R6\bin\XWin.exe cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 Stack trace: Frame Function Args 0022FB5C 00441891 (10036FF0, 00000000, 00980003, 0022FC1C) 0022FB9C 004475D5 (00020156, 00000311, 00020156, 00000000) 0022FBC8 77D13A5F (00446C50, 00020156, 00000311, 00020156) 0022FC30 77D13B2E (00000000, 00446C50, 00020156, 00000311) 0022FC60 77D17419 (00446C50, 00020156, 00000311, 00020156) 0022FC80 77D2BA3F (00446C50, 00020156, 00000311, 00020156) 0022FCAC 736DFD24 (00020156, 00000311, 00020156, 00000000) 0022FCD8 77D13A5F (736DFC4B, 00020156, 00000311, 00020156) 0022FD40 77D13B2E (00000000, 736DFC4B, 00020156, 00000311) 0022FD94 77D15874 (0097AF20, 00000311, 00020156, 00000000) 0022FDBC 77D158A4 (0022FDCC, 00000018, 0097AF20, 00000311) 0022FE24 77F4108F (00000000, 10036FF0, 0022FE64, 004CED9A) 0022FE64 004CEDBA (00000000, 10036FF0, 0022FEB4, 00401941) 0022FEB4 00401951 (00000007, 61564520, 10030278, 00000000) 0022FF10 61003F42 (00000000, 00000000, 00000003, 000113F3) 0022FF40 61004236 (004013E4, 00000003, 00000008, 81FF4000) End of stack trace (more stack frames may be present) Norbert > That is really bizarre. > > I'd like to take a look at this, but can you send in your /tmp/XWin.log > contents from when this happens? > > Harold > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED]]On Behalf Of Norbert Schmidt >> Sent: Wednesday, September 18, 2002 11:09 AM >> To: [EMAIL PROTECTED] >> Subject: minimized XWin is killed >> >> >> >> If I start remote windowmanager via ssh to my local _minimized_ >> fullscreened XWin, it disappears from desktop. (up to XWin-Test65.exe) >> >> (workaround is a remote script with "sleep 1" before starting Xsession in >> order to switch quickly from terminal to fullscreened XWin)
