http://bugs.winehq.org/show_bug.cgi?id=22490
Summary: _XReply: Assertion `!dpy->xcb->reply_data' failed. Product: Wine Version: 1.1.43 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl AssignedTo: wine-bugs@winehq.org ReportedBy: wanderer@fastmail.fm
I recently upgraded libxcb from version 1.1-1.2 to 1.5-3 (Debian package versions). Now, when I attempt to launch World of Warcraft in Wine, I get the following output:
../../src/xcb_io.c:445: _XReply: Assertion `!dpy->xcb->reply_data' failed. err:module:attach_process_dlls "opengl32.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\Program Files\World of Warcraft\Wow.exe" failed, status 80000101
I first saw this error with a version of Wine which I had been successfully using for some time - IIRC, it was 1.1.41, compiled from a git revision I don't recall. I have updated to the latest git version of Wine (wine-1.1.43-249-g033bb8a, commit 033bb8a2f9bd57000e64d5566f1b52a1cdf3f730) and recompiled, and the error persists. For what it is worth, I am running on an x86_64 system, but I have been able to use Wine without problems (aside from a peculiar lack of certain audio-output options) on this system for some time.
From what I can find online, this is an issue with many applications which use
xcb, and it is allegedly not an xcb bug but an application locking bug. It has been reported with OpenOffice, fglrxinfo, and various other programs; however, I am able to run all of those programs without errors. (I suspect that the bug may have been fixed in those programs.)
It is perhaps worth noting that every report of the problem which I have seen which mentioned video drivers came from someone who was using fglrx; I am also using fglrx, and had installed updated drivers along with the updated libxcb. However, since non-Wine OpenGL programs (such as fglrxinfo itself and glxgears) run for me without error, I suspect that the problem is in Wine rather than in fglrx.
I suspect that the problem would occur in other OpenGL programs run under Wine; however, the only such program to which I have immediate access is World of Warcraft itself. If the problem does in fact occur in other programs, then this bug should quite possibly be marked "major" instead of "normal" severity; I am leaving it as "normal" because I cannot currently confirm the failure with any other programs.
In some of the reports of this bug from other programs, it is claimed that downgrading libxcb makes the problem go away (http://forum.tuxx-home.at/viewtopic.php?f=10&t=565 being the best explanation I've found). However, I am not presently in a position to do so, as the package dependencies involved mean it would require downgrading Thunderbird from 3.x to 2.x, which is a nontrivial proposition.
I am aware that this is not remotely enough information to identify and fix the actual problem. I am quite willing to do almost any tests which might be asked for; just let me know what to do and what information to provide.
http://bugs.winehq.org/show_bug.cgi?id=22490
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2010-04-25 15:18:09 --- What video drivers? Have you tried upgrading those?
http://bugs.winehq.org/show_bug.cgi?id=22490
--- Comment #2 from wanderer@fastmail.fm 2010-04-25 16:45:55 --- As I said, I'm using the fglrx video drivers - the latest available via Debian stable/testing's fglrx-driver package - and this problem first manifested after I had updated both them and the xcb packages. There is no more recent graphics driver to update to.
Downgrading would be a reasonable suggestion, except that it's a royal pain, especially since this is the only version so far of these drivers to support Xorg 1.7; downgrading them would require downgrading X as well, and having done it at least once, I know that's nontrivial. (I'm also *not* eager to try downgrading fglrx, since even installing or upgrading it is a complicated process, compared to the nVidia drivers I was using last time I needed to downgrade X.)
http://bugs.winehq.org/show_bug.cgi?id=22490
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2010-04-25 19:02:34 --- (In reply to comment #2)
As I said, I'm using the fglrx video drivers
What exact version?
http://bugs.winehq.org/show_bug.cgi?id=22490
--- Comment #4 from wanderer@fastmail.fm 2010-04-25 19:52:50 --- The Debian package version is 10-3~prerelease-3 (the last number being the Debian package revision), which matches the other version numbers I've seen in my dealings with the driver. If there's a more specific place to look for the driver's internal version number, I don't know offhand where it is.
http://bugs.winehq.org/show_bug.cgi?id=22490
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Component|opengl |-unknown Resolution| |INVALID
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2010-04-26 00:41:32 --- Invalid. Please report this problem to your distro.
http://bugs.winehq.org/show_bug.cgi?id=22490
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2010-04-26 00:41:44 --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=22490
--- Comment #7 from wanderer@fastmail.fm 2010-04-26 08:25:35 --- Please explain how it's invalid - that is, where the problem actually lies - so that I know what to report to my distro.
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?
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.
http://bugs.winehq.org/show_bug.cgi?id=22490
--- Comment #9 from wanderer@fastmail.fm 2010-04-26 09:28:33 --- Okay; thanks. I can probably track it down far enough to at least figure out exactly which Debian packages to report the bug against.
(Of course, since these particular packages are AFAIK non-free, they may not be in a position to actually fix the problem - and upstream is far from the most responsive source out there... but that's not really your issue.)
Again, thanks for the advice, and I'll leave this bug alone now unless it *does* turn out to somehow be a Wine problem after all.
-
wine-bugs＠winehq.org