http://bugs.winehq.org/show_bug.cgi?id=2939
------- Additional Comments From inverseparadox@comcast.net 2005-07-05 18:01 ------- Yes, the "freeze" does represent a behaviour change; before the "can't change resolution/won't run" failure first occurred, upon completion the program would exit normally. Similarly, at first when the failure occurred, the window would close after I acknowledged the pop-up DDraw error. After a while, though, the behaviour changed to the one described - the window remains, unresponsive, until Wine is killed.
It takes me a while to track down change dates, since it takes at bare minimum fifteen minutes for a typical recompile and then I have to notice that it's done and go test, but with luck the new bug should show up before I have to go to work tomorrow evening. Unless someone specifically requests such, I won't post anything more to this one.
-
Wine Bugs