GLX broken on -current with nvidia drivers

After installing nvidia driver and kernel from SBo as I described in this post I found GLX was broken:

$ cat glxgears-error.txt 
Xlib:  extension "GLX" missing on display ":0".
Error: couldn't get an RGB, Double-buffered visual

Didn't trouble me too much as X worked fine otherwise but it did bother my daughter when she wanted to play minecraft!

I noticed the nvidia-switch script has lib version numbers that don't accord with -current but I understand from reading around that will be sorted when slackware RC1 comes along. I'm not sure what broke GLX but a workaround is to switch symlinks in /usr/lib64/xorg/modules/extensions back to the xorg libglx.so:

lrwxrwxrwx 1 root root       14 Jul 13 08:17 libglx.so -> xorg-libglx.so
lrwxrwxrwx 1 root root       14 Jul 13 08:18 libglxserver_nvidia.so -> xorg-libglx.so

About what RC1 you talk, when we still are with KDE4 shipped?

I thought the slackbuilds for Nvidia were known not to be OK for current? I'm using the Nvidia blob and current, here, and I had no problems. I can play minecraft, as well.

GLX gears works fine for me -current64, Plasma5, Nvidia 340.34 - switched back to open source from blob.

% ~ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
300 frames in 5.0 seconds = 59.948 FPS
X connection to :0.0 broken (explicit kill or server shutdown).

Are you using the most recent Minecraft launcher? It used to crash, but that was fixed. I am getting some errors when launching it, though:

[0713/112752.146465:ERROR:gl_context_glx.cc(232)] Couldn't make context current with X drawable.
[0713/112752.190269:ERROR:gles2_cmd_decoder.cc(4387)] GLES2DecoderImpl: Context lost during MakeCurrent.
[0713/112752.214146:WARNING:x11_util.cc(1349)] X error received: serial 283, error_code 168 (GLXBadWindow), request_code 150, minor_code 26 (X_GLXMakeContextCurrent)
[0713/112752.214233:ERROR:gles2_cmd_decoder.cc(4382)] GLES2DecoderImpl: Trying to make lost context current.
[0713/112752.214325:ERROR:gl_context_glx.cc(232)] Couldn't make context current with X drawable.
[0713/112752.225952:ERROR:gles2_cmd_decoder.cc(4382)] GLES2DecoderImpl: Trying to make lost context current.
[0713/112752.226983:WARNING:x11_util.cc(1349)] X error received: serial 308, error_code 8 (BadMatch (invalid parameter attributes)), request_code 150, minor_code 26 (X_GLXMakeContextCurrent)
[0713/112752.227014:ERROR:gles2_cmd_decoder.cc(4382)] GLES2DecoderImpl: Trying to make lost context current.
[0713/112752.227749:WARNING:x11_util.cc(1349)] X error received: serial 310, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)

I don't get these with MultiMC.

I'm referring to slackware RC1 - see this post by kingbeowulf:
https://www.linuxquestions.org/quest...ml#post6004714

I'll take a look at the binary itself from nvidia and check which minecraft launcher I'm using. Thanks for the replies.

That having been said, I was playing minecraft before bed last night and had a crash almost immediately after. It wasn't the usual hard lock I had with the Ryzen idling, but rather like my monitor reset, and then wouldn't come back. I'm not sure if it's related, or a continuance of the issues I was having. (I'm up to date on current's updates.) glxgears is fine. I did about 10 minutes of torture testing with mprime. memtest is fine. I'm inclined to think that the two issues aren't related, but bring it up, in case they are.