http://bugs.winehq.org/show_bug.cgi?id=24548
Summary: Zoo Tycoon Demo starts with black screen and white cursor Product: Wine Version: 1.3.2 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: wylda@volny.cz
Zoo Tycoon Demo starts with black screen and white cursor. Normally it would display start-up screen with loading progress bar, which is frozen (bug 16355).
1. I did a regression test between 1.3.1 and 1.3.2:
commit 22428d97e18e76ba76c10df945cf956ab1897101 Author: Henri Verbeet hverbeet@codeweavers.com Date: Wed Aug 25 20:46:49 2010 +0200
wined3d: Don't set a NULL container of type WINED3D_CONTAINER_TEXTURE.
Any container type other than WINED3D_CONTAINER_NONE implies a valid pointer of the specified type. This fixes a regression introduced by 368e5eb87ae983e4ea2f66b3ca2f4154b36bbcda.
:040000 040000 26b0cfc92fdfcc96a0aa2f0f09a12cf8ead0075e ab5bf090d4c67693f527a09c156ae74da9932c83 M dlls
2. No other bug report suffers from this commit, but this commit helped bug 24082.
3. Revert of this patch after git checkout makes that problem go away.
4. Adding author of this patch to CC.
--private keyword: bisected
http://bugs.winehq.org/show_bug.cgi?id=24548
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression URL| |http://www.gamershell.com/d | |ownload_4073.shtml CC| |hverbeet@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #1 from Wylda wylda@volny.cz 2010-09-27 23:22:37 CDT --- Created an attachment (id=30981) --> (http://bugs.winehq.org/attachment.cgi?id=30981) BAD log from wine wine-1.3.1-186
Forgot to mention... On the first game run switches to lower resolution and displays error window. When you keep the lower resolution for next run it no longer complains.
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #2 from Wylda wylda@volny.cz 2010-09-27 23:24:25 CDT --- Created an attachment (id=30982) --> (http://bugs.winehq.org/attachment.cgi?id=30982) GOOD log from wine wine-1.3.1-185
Even if this is a good trace, it interestingly begs for reporting to wine-devel :) I hope, that reporting here is enough ;)
http://bugs.winehq.org/show_bug.cgi?id=24548
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |16355
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #3 from Henri Verbeet hverbeet@gmail.com 2010-09-28 05:06:29 CDT --- Did it work before 368e5eb87ae983e4ea2f66b3ca2f4154b36bbcda? Does using the opengl ddraw renderer make any difference?
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #4 from Wylda wylda@volny.cz 2010-09-28 06:27:36 CDT --- (In reply to comment #3)
Did it work before 368e5eb87ae983e4ea2f66b3ca2f4154b36bbcda?
1.1.25 ==> works
1.1.30 ~ 1.3.0-277 ==> doesnot work (black screen as reported)
1.3.0-278 (aka 368e5eb87ae) ~ 1.3.1-185 ==> works as reported
1.3.1-186 ~ current git ==> doesnot work (black screen as reported)
Does using the opengl ddraw renderer make any difference?
Yes, but not in a good way. I used winetricks and choosed ddr=opengl. Then under 1.3.3-282-g440cf08 it displays the start-up screen for some time and then crashes (that ORM_FBO is there zillion times):
fixme:d3d:context_apply_blit_state Applying blit state for an offscreen target with ORM_FBO. This should be avoided.
err:seh:setup_exception_record stack overflow 2384 bytes in thread 0009 eip 7ed5424e esp 002409e0 stack 0x240000-0x241000-0x340000 ../../src/xcb_io.c:452: _XReply: Assertion `!dpy->xcb->reply_data' failed.
err:seh:raise_exception Exception frame is not in stack limits => unable to dispatch exception.
wine client error:9: write: Bad file descriptor
No backtrace :-( and that ORM_FBO reminds me bug 23173...
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #5 from Henri Verbeet hverbeet@gmail.com 2010-09-28 06:34:25 CDT --- Ok, so it looks like there's an older regression that temporarily went away due to the bug in 368e5eb87ae, and 22428d97e18e76ba76c10df945cf956ab1897101 brings it back. Anyway, I'll try to find some time to look at this.
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #6 from Wylda wylda@volny.cz 2010-09-28 06:42:52 CDT --- (In reply to comment #5)
Ok, so it looks like there's an older regression that temporarily went away due to the bug in 368e5eb87ae, and 22428d97e18e76ba76c10df945cf956ab1897101 brings it back. Anyway, I'll try to find some time to look at this.
Thanks :) If i read that correctly, it should be between .25 and .30. Unfortunately since on Debian Squeeze i don't have pre-prepared wine packages between .25 and .30. But i can do a regression test, if that would help you somehow.
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #7 from Wylda wylda@volny.cz 2010-09-28 08:26:19 CDT ---
You were right, it seems to me, that it comes from older times.
1. I did a regression test between 1.1.29 and 1.1.30:
commit a5214c306fd82982ed10fd8221ac00230186c9a6 Author: Henri Verbeet hverbeet@codeweavers.com Date: Wed Sep 16 08:37:15 2009 +0200
wined3d: Don't free D3D surfaces until the wined3d surface is destroyed.
This prevents for example a d3d9 depth stencil from being destroyed when it has no external references but is still in use by the device/stateblock. A nice side effect is that it simplifies handling of "implicit" surfaces like the frontbuffer and backbuffers, as well as the forwarding of reference counts for surfaces that are part of a texture.
2. There was another bug report suffering from this commit, see bug 23201.
3. Revert of this patch after git checkout makes that problem go away.
Tested under changed X resolution to 800x600 (not a windowed mode).
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #8 from Wylda wylda@volny.cz 2010-09-28 08:28:18 CDT --- Created an attachment (id=30997) --> (http://bugs.winehq.org/attachment.cgi?id=30997) GOOD log from wine-1.1.29-311 (reverted commit)
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #9 from Wylda wylda@volny.cz 2010-09-28 08:32:28 CDT --- Created an attachment (id=30998) --> (http://bugs.winehq.org/attachment.cgi?id=30998) BAD log from wine-1.1.29-312
These last two logs are easy to compare. Hopefully it will shine more light into the problem.
http://bugs.winehq.org/show_bug.cgi?id=24548
--- Comment #10 from Henri Verbeet hverbeet@gmail.com 2010-10-06 05:06:12 CDT --- For me this is fixed by 5fa84c56c344927dcb13b12409fbf64d738438f4.
http://bugs.winehq.org/show_bug.cgi?id=24548
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #11 from Austin English austinenglish@gmail.com 2010-10-06 12:14:26 CDT --- Yep, looks good here too, thanks!
http://bugs.winehq.org/show_bug.cgi?id=24548
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2010-10-15 12:50:52 CDT --- Closing bugs fixed in 1.3.5.