RE: Can't close windows; window-titles don't change with xserv 4. 3.0-40

RE: Can't close windows; window-titles don't change with xserv 4. 3.0-40

[Leeuw van der, Tim]

In a very dumb oversight I forgot to mention how I start the X Server:

In my 'Startup' folder there is a shortcut to XWin looking as follows

C:\cygwin\usr\X11R6\bin\XWin.exe -emulate3buttons -multiwindow -clipboard

In my environment the DISPLAY variable is set to ':0.0'

regards,

--Tim

>  -----Original Message-----
> From: 	Leeuw van der, Tim  
> Sent:	woensdag 14 januari 2004 10:44
> To:	'cygwin-xfree@cygwin.com'
> Subject:	Can't close windows; window-titles don't change with xserv
> 4.3.0-40
> 
> Hi,
> 
> Subject says it all, really - since upgrading to XWin 4.3.0-40, clicking
> the 'close' button on windows doesn't close them anymore. I do however
> have to hit the 'enter' key in rxvt windows before I can type anything
> again.
> The window-title doesn't change anymore, it's always 'Cygwin/X X'.
> 
> I've tested this with both rxvt and nedit (both cygwin packaged running
> locally).
> 
> The X server is the only Cygwin package that has been upgraded. Everything
> worked properly before the upgrade (and I use rxvt frequently as I don't
> like the dos windows) and the only other changes on this machine are:
> - Modified ClearCase settings
> - Removed some empty / non-existing / redundant directories from my PATH
> that were not cygwin-related.
> (Mentioning this just out of completeness but I can't see it having any
> impact on the XWin problem)
> 
> My machine: Win2k sp4; PIII; 512Mb. All cygwin at the latest versions (of
> course), ipc-daemon2 running. Any other relevant info that is required to
> tackle this problem?
> 
> (PS: I'm not on the list; trying to post anyways. Please include me in
> replies/followups...)
> 
> Regards,
> 
> --Tim van der Leeuw
> 

Re: Can't close windows; window-titles don't change with xserv 4. 3.0-40

[Leeuw van der, Tim]

> Nothing in your log states that the multi-window window 
> manager threads were aborting (but there are cases where they 
> abort silently, which I am trying to fix).
> 
> I will assume that your problem does not exist until you 
> succeed at reproducing it again. Okay?
> 
> Harold 

Hi,

Sorry for hitting 'send' on that message before I was finished with it; I
got distracted. I wanted to add that until I can reproduce it, let's close
the topic.

Greetings and thanks for the trouble,

--Tim

Re: Can't close windows; window-titles don't change with xserv 4. 3.0-40

[Harold L Hunt II]

Nothing in your log states that the multi-window window manager threads 
were aborting (but there are cases where they abort silently, which I am 
trying to fix).

I will assume that your problem does not exist until you succeed at 
reproducing it again.  Okay?

Harold

Leeuw van der, Tim wrote:

> Hi,
> 
> Here's the XWin.log file. It doesn't seem to mention anything at all
> regarding closing of windows failing, yet for sure I tried several times,
> several windows, and it didn't work.
> 
> It seems also that when I minimize a window, and restore it, the only way to
> get key-events working again is hitting the 'enter' key one or more times.
> 
>  <<XWin.log>> 
> 
> But.... now I restarted X, first without the -clipboard option and then
> again with -clipboard option, and can't reproduce the problem. I'm 99% sure
> though that I *did* restart X since I first observed this problem.

RE: Can't close windows; window-titles don't change with xserv 4. 3.0-40

[Leeuw van der, Tim]

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

Hi,

Here's the XWin.log file. It doesn't seem to mention anything at all
regarding closing of windows failing, yet for sure I tried several times,
several windows, and it didn't work.

It seems also that when I minimize a window, and restore it, the only way to
get key-events working again is hitting the 'enter' key one or more times.

 <<XWin.log>> 

But.... now I restarted X, first without the -clipboard option and then
again with -clipboard option, and can't reproduce the problem. I'm 99% sure
though that I *did* restart X since I first observed this problem.

[-- Attachment #2: XWin.log --]
[-- Type: application/octet-stream, Size: 3606 bytes --]

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
winInitializeDefaultScreens - Returning
OsVendorInit - Creating bogus screen 0
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
(EE) Unable to locate/open config file
InitOutput - Error reading config file
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - Allowing PrimaryDD
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 0000001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winScreenInit - dwWidth: 1024 dwHeight: 768
winSetEngine - Multi Window => ShadowGDI
winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel
winCreateBoundingWindowWindowed - User w: 1024 h: 768
winCreateBoundingWindowWindowed - Current w: 1024 h: 768
winAdjustForAutoHide - Original WorkArea: 0 0 715 1024
winAdjustForAutoHide - Adjusted WorkArea: 0 0 715 1024
winCreateBoundingWindowWindowed - WindowClient w 1024 h 715 r 1024 l 0 b 715 t 0
winCreateBoundingWindowWindowed -  Returning
winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 715 depth: 16
winAllocateFBShadowGDI - Dibsection width: 1024 height: 715 depth: 16 size image: 1464320
winAllocateFBShadowGDI - Created shadow stride: 1024
winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f
winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16
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
winInitMultiWindowWM - Hello
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winInitWM - Returning.
winFinishScreenInitFB - returning
winScreenInit - returning
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
InitOutput - Returning.
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409) 
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)"
winPointerWarpCursor - Discarding first warp: 512 357
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
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display.
winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning.
winDeinitMultiWindowWM - Noting shutdown in progress
OsVendorReset - Hello
winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.
OsVendorReset - Clipboard thread has exited.

winClipboardIOErrorHandler!