Got an error out of a Java OpenGL based application:

GLFW error 65543: GLX: Failed to create context: GLXBadFBConfig.

I'm affected. I updated all my packages after 1 month of not using the computer and now a wine game using DXVK is running with 3 fps, while before it ran with 100 fps. I cannot pinpoint the culprit to be the nvidia package since I updated so many packages.

In my case even DXVK (Vulkan) seems to be affected.

NVIDIA RTX 2060 card.

The issue was fixed by installing the testing version of the package from the testing repo: nvidia-495.44-4

Give that a try for now I assume someone just did a dumb and it will be good in a day or two.

I installed nvidia 495.44-4 from testing and rebooted. Now the game won't even start, I get a wine message box titled "Fatal Error" with the message "No suitable display adapter found.".

I don't know if related, but after upgrading to 495.44, kwin always crashes on startup (I'm using X11, Wayland session does not even start now). I have to manually go to the compositor settings page, force renable to get the system bask to work as usual. I also had some random crashes. All these issues went away downgrading to 470.74.

I attach a log from journalctl -p err showing the kwin crash at startup, in case is useful.

Can you guys post the output of nvidia-smi?

This is my output with the game running at 3 fps with 495.44-3.

Just making sure: You have lib32-nvidia-utils installed?

Yes I had it already, lib32-nvidia-utils-495.44-1

Is your GPU set to some powersaving mode? Can you check nvidia-settings?

Here are some screenshots of my nvidia-settings

Does it do anything if you force it to performance mode? I really got no idea what might be wrong here at this point though speaking from a packaging perspective. Everything appears to be good from what I can see here. I got a 2080 Ti so my settings look very similar to yours all things considered.

I tried setting preferred mode to "Prefer Maximum Performance", with no change.
I have now downgraded to these packages:

nvidia-470.74-7-x86_64.pkg.tar.zst
nvidia-dkms-470.74-1-x86_64.pkg.tar.zst
lib32-nvidia-utils-470.74-1-x86_64.pkg.tar.zst
libxnvctrl-470.74-1-x86_64.pkg.tar.zst
nvidia-settings-470.74-1-x86_64.pkg.tar.zst
nvidia-utils-470.74-1-x86_64.pkg.tar.zst

These are all and only packages that I have downgraded. After a reboot game runs smoothly with no further action needed. So I can now confirm it is really some kind of problem with the nvidia packages. Maybe not a packaging issue, but an upstream bug?

I have prime laptop configuration, if that's relevant.

Can you confirm that while a game is running, it's actually ran on the Nvidia GPU at all? Perhaps it's using the integrated GPU instead. This is really my only guess at this point.

Driver 495.44 if full of bugs. This is clearly Nvidia's problem and not an Arch issue. We can only wait and try the driver when there is a new release. I can reproduce my issue with Plasma in a different device running a different distro.

Thanks for that confirmation! I'm inclined to close this issue then as upstream. It's not great but I don't see anything we can do here from our side.

Just as a reminder. The nvidia-495.44-4 version from testing resolved the issue for me. Also note three minor revision releases within a couple hours of each other on mainline which is indicative of a packaging issue.

> Also note three minor revision releases within a couple hours of each other on mainline which is indicative of a packaging issue.

It's not as you can clearly see from the commit messages: https://github.com/archlinux/svntogit-packages/commits/packages/nvidia/trunk

Those were all kernel module rebuilds for each respective kernel. 495.44-4 is for kernel 5.15, both being in testing. It's definitely worth a shot, though.

I got mine to function properly by utilizing an older config I had laying around. It appears the .drirc file in the home directory fixes this issue. I have also attached my .nvidia-settings-rc This combination works properly. And I'm not sure why.

Edit: did the usual delete and reboot. .drirc seems to not have any affect. What did work was nuking my configs and putting the old ones back though.

Chad: are you also using the kernel 5.15.1 from testing? Maybe this driver does not work well with 5.14? I use the nvidia-dkms, so all those changes in pkgrel are only related to rebuilds for newer kernel versions. I guess I will give it a try when 5.15.1 goes into [core]. For now, I stay with 470.74.

Nvidia optimus laptop:
Wine applications using prime-run (from package nvidia-prime) also not working.
Downgrading to nvidia 470.74 solves problem.

Today I updated all the packages, including the new linux 5.15.2.arch1-1 kernel, and reverted my nvidia downgrade, so I'm back to nvidia 495.44-3.
I also installed optimus-manager-qt from AUR and set it to "Hybrid mode". To my understanding that should have been the default even before installing optimus-manager, so I don't know if this was relevant.
After doing this, the game now runs fine! I don't know if it is because of optimus-manager or because of all the updates.

Still same issue for with 5.15.2 + nvidia 495. I'm using nvidia-470xx from AUR until a new release from Nvidia.

I'm having the issue again! I don't know what triggered it back.... Now even selecting Nvidia card only in optimus-manager still makes the game with 3 fps.

I still have nothing in this bug report that is indicative of a packaging problem. I'm inclined to close it as it's no use to track this downstream for a binary blob package.