nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   180.16: GLXBadDrawable error on starting wine a second time (http://www.nvnews.net/vbulletin/showthread.php?t=124730)

coolphoenix 12-15-08 03:47 PM

180.16: GLXBadDrawable error on starting wine a second time
 
1 Attachment(s)
i'm getting the following error after starting wine a second time (this means, i start a program with wine, everything works, i close the program and then i want to start it again or another one with wine --> error):

Code:

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:  456
  Current serial number in output stream:  456

i found some old threads saying this error was corrected (so it was a problem of the driver, not wine), but i still have it. this happened also to me also before on other 180.x drivers, but don't know when it started because i thought my program was causing the error - but the error happens on my second program too.

using 2.6.28-rc6 gentoo x64, wine 1.1.10

any workaround known? or is this a wine-bug now?

regards

edit: i forgot, restarting the xserver allows me to start a program again once before the problem occurs again

xianthax 01-04-09 12:31 PM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
I have this problem as well with 180.18, same exact error. I've also occasionally seen what i think is the same thing in other openGL applications such as google earth, first run and shutdown is fine, the app then crashes on subsequent launches. Rebooting the x server allows apps to run again.

Ubuntu 8.10, gnome, metacity
Wine 1.1.12
2 x 8600GTS, 4 x screens, xinerama enabled

Wine error output:

Code:

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:  460
  Current serial number in output stream:  460
Locking assertion failure.  Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x7e3ca7c7]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0x7e3ca96e]
#2 /usr/lib/libX11.so.6 [0x7e411619]
#3 /usr/lib/libX11.so.6(XESetCloseDisplay+0x44) [0x7e3f3294]
#4 /usr/lib/libGL.so.1 [0x7d657f69]

cheers,

x

voltaicsca 01-08-09 03:28 AM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
I am having the same issue.
after starting X, World of Warcraft will start fine the first time, but then any subsequent launches fail with the following error:
Code:

X Error of failed request:  GLXBadDrawable
  Major opcode of failed request:  144 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  151
  Current serial number in output stream:  151
ft/WoW.exe: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
err:module:attach_process_dlls "opengl32.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"L:\\WorldofWarcraft\\WoW.exe" failed, status 80000101

launching WoW works every time using the 177.82

Running 3 screens using xinerama on xorg-server-1.3.0.0-r6
uname -srp:
Code:

Linux 2.6.26-gentoo-r3 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz

incidenta5 01-09-09 02:49 AM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
I have the exact same problem as the OP. This occurs using the 180.22 driver if I use Xinerama across all 3 of my monitors.

If I disable two of them and restart X I can start and restart the same application without a problem.

Linux 2.6.27.9-159.fc10.x86_64 x86_64
NVIDIA 180.22 Driver

incidenta5 01-11-09 05:28 AM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
This also happens if you try executing the following program compiled for windows under wine. After digging through the code it ends up failing with a call to pwglGetProcAddress.

Not sure if this is a wine or nvidia problem at this point.

Code:


#include <windows.h>
int main()
{
    LoadLibrary( "opengl32.dll" );
    return 0;
}


Thunderbird 01-11-09 05:36 AM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
It is an nvidia bug because it didn't happen on some earlier drivers. I have a bugreport for this in wine and there people investigated this for me. By head 100.x or so didn't have this problem. I can't look up the bug right now since bugs.winehq.org is down.

klikklak 01-26-09 02:16 PM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
I'm bumping this because I have the same thing, three screens xinerama, 180.22, 2x8600gt's. Fails to run wow after starting nexuiz.

Felix.K 01-30-09 07:36 AM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
I have exactly the same problem with driver version 180.22 x64.

Could anyone fix this problem or provide some better workaround than restarting X?

Felix.K 02-09-09 02:40 PM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
I've tried disabling xinerama and suddenly the problem disappeared.

So it seems to be a problem with xinerama and the NVIDIA driver.
The wine developers think its a driver problem, see:
http://bugs.winehq.org/show_bug.cgi?id=16311

mrselfpwn 02-11-09 05:09 PM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
I have the same issue using 180.29 (latest driver). I am also using Xinerama view with two monitors. My video card is the Nforce 8800 GTX.
Thanks again.

AaronP 02-11-09 09:50 PM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
Thanks for reporting this. I managed to reproduce the problem and filed a bug.

xianthax 02-11-09 10:27 PM

Re: 180.16: GLXBadDrawable error on starting wine a second time
 
Quote:

Originally Posted by Felix.K (Post 1927242)
I've tried disabling xinerama and suddenly the problem disappeared.

So it seems to be a problem with xinerama and the NVIDIA driver.
The wine developers think its a driver problem, see:
http://bugs.winehq.org/show_bug.cgi?id=16311

i had the same problem when using xinerama, have since not been using xinerama since 180.22 or so and not had the problem....

the mouse hang in xinerama was more annoying tbh but atleast it had a work around...

also in my case i gain about 25% performance from not using xinerama as well...

cheers,

x


All times are GMT -5. The time now is 07:16 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.