[Pkg-fglrx-devel] Bug#579813: Bug#579813: ../../src/xcb_io.c:445: _XReply: Assertion `!dpy->xcb->reply_data' failed.

[Michael Gilbert]

reassign libxcb1
thanks

On Fri, 30 Apr 2010 21:54:18 -0400 The Wanderer wrote:
> I should start out by saying that I am not 100% certain that this bug is
> in fglrx-driver; it also might be in libxcb, in Wine, or somewhere
> (else) in the OpenGL or GLX stack, or even in X. I am reporting it under
> fglrx-driver because I have to pick some package, and fglrx seems the
> most likely candidate.
> 
> I track stable and testing. Fairly recently, I noticed that the fglrx-*
> packages could now be updated without needing to remove xserver-xorg*,
> and ran a partial dist-upgrade (omitting packages which have active bugs
> unless I can specifically determine that they don't affect me). In the
> process, both fglrx-driver and libxcb* were updated.
> 
> After the update, I attempted to launch World of Warcraft under Wine.
> Instead of launching successfully (as it had been doing before the
> update), it exited before really getting started, with only the
> following console 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 don't really see how this could be a fglrx bug.  the error refers to
opengl.dll, which probably lead to your conclusions, but that is
provided by wine; not fglrx. libxcb appears to have gone through quite
a few changes recently, and my best guess is that the problem was
introduced there.

the latest fglrx is 10-4, and you could try upgrading, but it probably
won't make a difference.  can you reproduce the problem with the free
radeon driver?

mike