http://bugs.winehq.org/show_bug.cgi?id=32621
--- Comment #2 from Michael Stefaniuc mstefani@redhat.com 2013-01-01 18:26:21 CST --- Of course even easier is to just check 841214ddb4d4dc620e6b51dfe6655b585d423edc with the patch from a0f039a6049641cc2be8fa32f2afa3c3f394a99b. That should fail while still allowing you to reproduce the issue.