http://bugs.winehq.org/show_bug.cgi?id=31882
--- Comment #14 from Erich Hoover ehoover@mines.edu 2012-10-08 11:16:11 CDT --- (In reply to comment #13)
... Although the root cause seems to be the same, the libxcb bug is exposed through a different code path/module in Wine. If you mark this bug a dupe of bug 31406 you should make a better summary there because it affects a _wide_ range of apps. Another option could be to close this upstream too and keep it separate to collect all dupes containing winex11 surface deadlocks here. ...
This particular bug is actually a different problem in XCB (https://bugs.freedesktop.org/show_bug.cgi?id=40372 , http://cgit.freedesktop.org/xcb/libxcb/commit/?id=5ceeaaa4294201b3f613c07f9e...). I also ran into this bug since I started with an old libxcb. As a result I discovered that it's easy to upgrade libxcb independent of the rest of X11, so we could try and convince the distros to push libxcb 1.9 to older releases. I'm not sure what the best option is to help people out wrt. them running into issues with older releases, I'm sure you have much more experience dealing with that then I do.