http://bugs.winehq.org/show_bug.cgi?id=21540
--- Comment #6 from Henri Verbeet hverbeet@gmail.com 2010-03-08 15:04:55 --- For what it's worth, the AMD bug report got a reply saying they were able to reproduce and identify the issue. I assume that means the bug will be fixed in some future fglrx release.