GLXBadDrawable 142 (Gentoo) (works fine on Ubuntu)

[Dutchy]

Gentoo 2008.0 beta2 amd64 (portage: ~amd64)

So I've been getting this error on multiple applications (not just TmNF):

dutchy@vampire ~/.wine/drive_c/Program Files/TmNationsForever $ wine TmForeverLauncher.exe
X Error of failed request: GLXBadDrawable
Major opcode of failed request: 142 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 503
Current serial number in output stream: 503

since it works fine on ubuntu, there must be something wrong with my configuration (either wine or gentoo), but I have no idea where to start. Any help at all would be appreciated.

It got really weird when suddenly it did start, perhaps nvidia failed and it used some sort of fallback? I have a screenshot and logs for that:
http://dragon.student.utwente.nl/pics/s ... driver.png
http://dragon.student.utwente.nl/pics/s ... driver-log
I can't recreate this at will, it just happens.

I have found http://www.nvnews.net/vbulletin/showthr ... ?p=1630681 which is a similar error, but since I do not have BSD the solution does not apply to me (if it does, tell me how in linux )

Finally, I'll list some versions

wine: 1.0-rc2 (but rc1 did the same)
nvidia-drivers: 169.12
xorg-server: 1.4.0.90-r3

dutchy@vampire ~ $ uname -r
2.6.25-gentoo-r4-metal

while I'm at it, I'll add my xorg.conf too:
http://dragon.student.utwente.nl/pics/s ... /xorg.conf

I've probably forgotten to mention something, tell me if you need more info.

[vitamin]

Gentoo 2008.0 beta2 amd64 (portage: ~amd64)

So I've been getting this error on multiple applications (not just TmNF):

dutchy@vampire ~/.wine/drive_c/Program Files/TmNationsForever $ wine TmForeverLauncher.exe
X Error of failed request: GLXBadDrawable
Major opcode of failed request: 142 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 503
Current serial number in output stream: 503

Looks like this bug to me: http://bugs.winehq.org/show_bug.cgi?id=13101

[Dutchy]

I could be that bug, however, setting antialiasing to off or to 8x or higher does not 'fix' it as it does for them.

(At least, nvidia-settings changes this on the fly? there is no save/apply button and generating a new xorg.conf does not set an antialias-setting)

Also, in ubuntu I'm using 169.12 too, with a 2.6.24 kernel (synaptic says 169.12+2.6.24.12-17.36)

[Dutchy]

Posting a new reply for my edit, i dont think editting works for the mailinglist

In ubuntu I'm using 169.12 too (synaptic says 169.12+2.6.24.12-17.36)

dutchy@vampire:~/.wine/drive_c/Program Files/TmNationsForever$ uname -r
2.6.24-17-generic