Re: XWin -multiwindow menu problem (Was: XWinrc bugs)

[Brian Chase <networkr0 at cfl dot rr dot com>]

I've had some problems with XWin as well, here's what I get:

networkr@brian ~
$ export DISPLAY=:0

networkr@brian ~
$ Xwin -multiwindow -clipboard &
[1] 2068

networkr@brian ~
$ Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.7.0.0-4

Contact: cygwin-xfree@cygwin.com

XWin was started with the following command line:

Xwin -multiwindow -clipboard

OsVendorInit - Creating bogus screen 0
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winValidateArgs - Returning.
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 00000007
winScreenInit - dwWidth: 1280 dwHeight: 1024
winSetEngine - Multi Window or Rootless => ShadowGDI
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per 
pixel
winCreateBoundingWindowWindowed - User w: 1280 h: 1024
winCreateBoundingWindowWindowed - Current w: 1280 h: 1024
winAdjustForAutoHide - Original WorkArea: 0 0 996 1280
winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280
winCreateBoundingWindowWindowed - WindowClient w 1280 h 996 r 1280 l 0 b 
996 t 0

winCreateBoundingWindowWindowed -  Returning
winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 996 depth: 32
winAllocateFBShadowGDI - Dibsection width: 1280 height: 996 depth: 32 
size image
: 5099520
winAllocateFBShadowGDI - Created shadow stride: 1280
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 
bpp 32
winRandRInit ()
winCreateDefColormap - Deferring to fbCreateDefColormap ()
null screen fn ReparentWindow
null screen fn RestackWindow
winFinishScreenInitFB - Calling winInitWM.
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitWM - Returning.
winFinishScreenInitFB - returning
winInitMultiWindowWM - Hello
winMultiWindowXMsgProc - Hello
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
winScreenInit - returning
InitOutput - Returning.
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack 
of shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409)
(EE) Keyboardlayout "US" (00000409) is unknown
Rules = "xorg" Model = "pc101" Layout = "us" Variant = "(null)" Options 
= "(null
)"
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
from li
st!
winPointerWarpCursor - Discarding first warp: 640 498
winBlockHandler - Releasing pmServerStarted
winInitMultiWindowWM - pthread_mutex_lock () returned.
winBlockHandler - pthread_mutex_unlock () returned
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened 
the disp
lay.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully 
opened the di
splay.
winClipboardProc - XOpenDisplay () returned and successfully opened the 
display.

winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.

then it locks up...................




Rodrigo Medina wrote:

> Hi Earle,
>
> At Sun, 18 Apr 2004 22:35:12 -0700 Earle F. Philhower, III wrote:
>
>  
>
> > That's good troubleshooting, a patch that works around the W95 bug
> > was committed to CVS.  (Are you able to run the latest cygwin DLLs
> > under W95 still?  When I was running cygwin w/W95A+IE5.5sp2 under
> > bochs I got nothing but bluescreens in cygwin1.dll...)
> >    
>
> I have been working with cygwin/X  under Win95 for more than 2 years
> without too much problem. Lately, from cygwin1 1.5.6 up to 1.5.9 there
> was a bug with threads that crashed XWin -multiwindow. This problem was
> solved in the more recent snapshots. As I understand that there are
> difficulties to check the new software in Win95, I have decided to try
> all new snapshots and versions of XWin as soon as possible.
>
> bye
> Rodrigo Medina
> 					  	
>  					  	
>