The problem described below starts with wine-0.9.42 and continues to exist on wine-0.9.43. Should be related to Gentoo, because wine-0.9.43 compiled on my Debian/Sid doesn't show this bug. Steps to reproduce: Gothic 1 must be installed and should display in a window, not fullscreen. Open an xterm, cd to JoWood/Gothic/system. Then start Gothic with 'wine GOTHIC.EXE'. http://www.triffids.de/pub/wine/0.9.43/w1.jpg (182 KB) Top on the left side ist the xterm, on the right side is a part of the beginning Gothic 1. Obviously it is neccessary, to move the Gothic window to the left. :) http://www.triffids.de/pub/wine/0.9.43/w2.jpg (188 KB) All is fine until the moment, when the menu of Gothic should appear. Instead of that the following window appears: http://www.triffids.de/pub/wine/0.9.43/w3.jpg (8 KB) Clicking of OK ends wine. The full log can be seen here: http://www.triffids.de/pub/wine/0.9.43/err_log.txt.bz2 Reproducible: Always If you need more information, please tell me, how i can obtain them. Meanwhile i have binaries of 38, 40, 41, 42 and 43 on my Gentoo. *g* I have also tested with a new ~/.wine, but that makes no difference. Gentoo: kernel 2.6.21-gentoo-r4 xorg-x11 7.2 nvidia-drivers 100.14.11 Sid: kernel linux-2.6.21.4 xorg 1:7.2-5 nvidia-glx 100.14.11-1
(In reply to comment #0) > If you need more information, please tell me, how i can obtain them. Eehm, here is one. Forgot emerge --info. http://www.triffids.de/pub/wine/0.9.43/emerge-info.txt
Additional information: A normally compiled wine-0.9.43 on my Gentoo, without ebuild, shows the same error. But not on my Debian/Sid. Hm. For clarification, on Gentoo all is fine, unless the window with gothic is moved or i switch to another workplace and then back. This triggers the error message with D3DXERR_CAPSNOTSUPPORTED Gentoo: hafi@t900 ~ $ gcc --version gcc (GCC) 4.1.2 (Gentoo 4.1.2) Sid: hafi@t900:~$ gcc --version gcc (GCC) 4.1.3 20070718 (prerelease) (Debian 4.1.2-14) Interesting problem. :)
A new test on my Sid with 0.9.43 now shows the same error and i don't know, what has changed. So it seems now that this bug isn't Gentoo related and should be moved upstream. Sorry for the noise.
