Bug description: I am trying to run Warcraft III Frozen Throne using wine. On startup, the resolution will change (from 1280x800 to 1024x768) and then suddenly the whole screen will just become garbled. At this time, I can still move the mouse pointer. About 2 seconds later, the screen will go blank for a short moment and then come back to be garbled again. At this time, I can't move the pointer anymore, and the system doesn't repond to CTRL + ALT + Backspace. SSH in to machine will show the process /usr/bin/X taking up 100% CPU. I am able to run the game on another machine with all the exact software version (xserver, mesa, drm, kernel, wine) except that it has nvidia instead of intel for video driver. System environment: -- chipset: G965 -- system architecture: x86_64 -- xf86-video-intel: xf86-video-i810-2.3.1-r1 -- xserver: xorg-server-1.4.0.90-r3 -- mesa: mesa-7.0.3 -- drm: libdrm-2.3.0 -- kernel: 2.6.25-tuxonice-r1 -- Linux distribution: Gentoo -- Machine or mobo model: Lenovo 3000 Y410 Reproducing steps: 1. wine Frozen\ Throne.exe 2. garbled screen Additional info: FWIW, Diablo II runs fine
Created attachment 16715 [details] Xorg.0.log
Created attachment 16716 [details] xorg.conf
Created attachment 16717 [details] dmesg
Created attachment 16718 [details] output from wine with LIBGL_DEBUG=verbose
> wine Frozen\ Throne.exe I can't help you, but it looks like you aren't playing in OpenGl mode? (Ord did you set the setting in regedit?) - So it won't run playable anyway. Try this out: wine Frozen\ Throne.exe -opengl
Nope, still crashed with the -opengl flag. FYI, the game runs perfectly fine without the -opengl flag on my other machine with nvidia driver (as mentioned in the bug description).
Just to report that the game is playable now. System environment: -- chipset: G965 -- system architecture: x86_64 -- xf86-video-intel: xf86-video-intel-2.7.0 -- xserver: xorg-server-1.6.0 -- mesa: mesa-7.4 -- drm: libdrm-2.4.6 -- kernel: 2.6.29-tuxonice-r1 (with the tiling patch) -- Linux distribution: Gentoo -- Machine or mobo model: Lenovo 3000 Y410
I am also unable to reproduce this bug on current Mesa master. Closing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.