[Bug 2947] New: Window remains, frozen, on program exit until Wine is killed by hand

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2947

Summary: Window remains, frozen, on program exit until Wine is
                    killed by hand
           Product: Wine
           Version: CVS
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wine-binary
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

I'm not positive that this (wine-binary) is the correct component to reference,
but it seems as appropriate as any of the others and more so than some; if
anyone knows better, please feel free to change that assignment.

I first noticed this bug while still suffering under the effects of bug 2939
(sorry, I don't know how to make that a link, unless it's just a matter of
writing the HTML directly), and described it briefly there before that bug was
fixed.

I use Wine, among other purposes, to play Might and Magic VI, which runs all but
perfectly. In current CVS, however, when the program concludes and exits -
whether because of some failure or because of a user-entered Exit command - the
program window does not close, and Wine does not release the terminal from which
it was started; the window will no longer update, but remains frozen until Wine
is killed by some means (Ctrl-C or Ctrl-Backslash in the terminal both work).

The version of Wine I get by

cvs -z3 update -dPA "2005-04-27 03:15:00 CDT"

does not exhibit this problem, and the version I get by

cvs -z3 update -dPA "2005-04-27 03:19:00 CDT"

does. There is exactly one commit between those times, according to the wine-cvs
archive.

Oddly enough, there is a behaviour which looks more as if it should be the fault
of the window manager than of Wine which was not present before bug 2939 cropped
up, is present in the earlier of these two versions, and is not present in the
later (and also not in the latest CVS). It may not be worth noting, because it
doesn't exist currently, but there's a chance that fixing this bug may cause it
to return; if anyone thinks it's relevant, simply ask and I can try to describe it.