Cygwin X11 server, notepad and message boxes

[Krzysztof Foltman]

I'm trying to run notepad on WINE, with DISPLAY environment variable 
pointing to Cygwin (X Server 6.7.0.0-12) running on my Windows XP 
machine. It works rather OK-ish, but when I try to close Notepad, it 
gets stuck in GetMessageW function call after displaying a "text 
changed, do you want to save ?" dialog box:

trace:msg:GetMessageW (1117) mask=0000007f, bits=00000000, 
changed=00000000, waiting
0009:Call kernel32.ReleaseThunkLock(406ce6f8) ret=409b79a3
0009:Ret  kernel32.ReleaseThunkLock() retval=00000000 ret=409b79a3
0009:Call 
x11drv.MsgWaitForMultipleObjectsEx(00000001,403893f4,ffffffff,00000000,00000000) 
ret=409b79c7
0009:Call 
kernel32.WaitForMultipleObjectsEx(00000001,403893f4,00000000,ffffffff,00000000) 
ret=40ce1838
0009:Call 
ntdll.NtWaitForMultipleObjects(00000001,406ce32c,00000000,00000000,00000000) 
ret=404e8989

I guess the bug is not in notepad, but in Wine message handling, as it's 
not the only program, that freezes after displaying a dialog box. It 
doesn't happen when MessageBox is called from WM_KEYDOWN handler, but it 
DOES happen when MessageBox is called from WM_CLOSE handler, but only if 
WM_CLOSE was sent by system after clicking Close or presing Alt+F4, and 
not sent or posted by application itself.

http://foltman.com/wintest-dlginclose.zip

Any idea what it may be ? deadlock ? The version of Wine I'm using was 
grabbed a couple of hours ago from anonymous CVS.

Krzysztof

[Brian Vincent]

On Wed, 23 Feb 2005 11:29:40 +0100, Krzysztof Foltman
<kfoltman(a)portal.onet.pl> wrote:
> I'm trying to run notepad on WINE, with DISPLAY environment variable
> pointing to Cygwin (X Server 6.7.0.0-12) running on my Windows XP
> machine. It works rather OK-ish, but when I try to close Notepad, it
> gets stuck in GetMessageW function call after displaying a "text
> changed, do you want to save ?" dialog box:

fwiw, I'm having the same problem and I'm running notepad directly on
my local machine.  I last compiled Wine about 4 days ago, so the
problem appeared sometime before that.

-Brian