http://bugs.winehq.org/show_bug.cgi?id=22490
--- Comment #8 from Henri Verbeet hverbeet@gmail.com 2010-04-26 08:35:20 --- (In reply to comment #7)
As I said in the original report, although the problem did manifest on updating both libxcb and the fglrx drivers, all information I have found online claims that past occurrences of this error message have been due not to a bug in either of them but to one in the application calling libxcb. In this case, that would appear to be Wine, specifically libopengl32.dll. Is that not the case? If so, what *is* actually going on?
Wine doesn't call libxcb directly, if it happens during opengl32 initialization it's probably the result of some GLX call. Running with WINEDEBUG="+synchronous,+wgl" may help with tracking down the specific call or sequence of calls, but it's unlikely to be a Wine problem.