http://bugs.winehq.org/show_bug.cgi?id=34238
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM
--- Comment #39 from Rico kgbricola@web.de 2013-09-12 01:56:26 CDT --- There is no mesa release with the fix, yet. It will likely take some weeks... There is nothing we can do about that!
Imho, you can (if you have the knowledge or you may ask the corresponding forums / help channels). Your solutions are: - use wine <= wine-1.5.28 (use a package or build wine from source), mesa version doesn't matter - compile mesa from source (git >= 8b302e1635534bfc6ed3ad671f2428470b3a765d) or use a fixed package (likely your distribution doesn't ship one, yet), wine version shouldn't matter - use another graphics card which doesn't trigger the bug (either one with GL>=2.1 and mesa or some amd/nvidia with the corresponding drivers) - wait till your packages ship the fixes ...
I'm not sure if I said all possible solutions, but all this solutions have nothing to do with wine or this bug at all. Please stop posting / changing the bug and don't reopen. For us it is an upstream bug! If you need help, ask in the wine forum (e.g. http://forum.winehq.org/viewtopic.php?f=8&t=19536 ), better in the help channel for the problem you like to solve (mesa / ubuntu / hardware distributor).