http://bugs.winehq.org/show_bug.cgi?id=19470
Summary: Wine shouldn't assume the default visual supports GLX Product: Wine Version: 1.1.26 Platform: PC OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: minor Priority: P2 Component: winex11.drv AssignedTo: wine-bugs@winehq.org ReportedBy: cdavis@mines.edu
Created an attachment (id=22631) --> (http://bugs.winehq.org/attachment.cgi?id=22631) Output from glxinfo command
Right now, when initializing OpenGL support, and determining the OpenGL capabilities of the host system (in X11DRV_WineGL_InitOpenglInfo()), Wine makes a very crucial assumption: that the default visual supports GLX. This is not necessarily true, so therefore Wine should not make this assumption.
In the 2.4.0 release candidate from the Xquartz project, for example, the default visual does not support GLX. The fact that it doesn't caused the glXCreateContext() call in the mentioned function to fail.
In particular, that call to glXCreateContext() fails with the following message:
X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 0 () Value in failed request: 0x22 Serial number of failed request: 515 Current serial number in output stream: 515
That value in the message happens to be the ID of the default visual on my system. Under 2.4.0 RC1, that visual doesn't support GLX. (In the next 2.4.0 RC, it will, for reasons which become apparent in the next paragraph.) I've attached the output from glxinfo under that version, so you can see for yourself.
I filed a bug with Xquartz (http://xquartz.macosforge.org/trac/ticket/287). They told me they would fix it (and they did, and the fix is going into the next 2.4.0 RC), but they also warned me that the default visual for a given display and screen doesn't have to support GLX, and that I should report this to WineHQ.