http://bugs.winehq.org/show_bug.cgi?id=18502
asuffield@suffields.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #8 from asuffield@suffields.me.uk 2009-05-25 14:03:59 --- An intensive debugging session finally tracked down the problem. The thing you have to realise is that glxinfo is *worthless* for debugging wine on amd64 platforms, since it uses the long mode userspace, while wine uses the ia32 emulation layer.
The correct way to debug this class of problems is to use WINEDEBUG=wgl, and observe these lines:
0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo GL version : 1.4 (3.0.0 NVIDIA 180.44). 0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo GL renderer : GeForce 8400 GS/PCI/SSE2. 0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo GLX version : 1.4. 0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Server GLX version : 1.4. 0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Server GLX vendor: : NVIDIA Corporation. 0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Client GLX version : 1.4. 0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Client GLX vendor: : SGI. 0009:trace:wgl:X11DRV_WineGL_InitOpenglInfo Direct rendering enabled: False
Which tells us: oh damn, client GLX vendor of SGI means that's mesa-glx, we're missing the ia32 version of the nvidia libGL, so half the extensions aren't working right. The part of the driver that loads into the X server is fine, so it seems fine everywhere else.
This issue has been misdiagnosed numerous times, resulting in much confusion.