Segfault with latest kernel and nvidia card

I am seeing a segmentation fault with the nvidia driver when updating to the latest kernel with ‘dnf update’.

Jan 27 17:27:36 localhost kernel: QSGRenderThread[515634]: segfault at 89 ip 00007f5a76dbcd84 sp 00007f5a6995f330 error 4 in libnvidia-glcore.so.390.132[7f5a75ff4000+141f000]
Jan 27 17:27:36 localhost kernel: Code: 44 24 40 0f b6 44 24 40 48 89 55 48 88 45 40 8b 45 28 ff c0 89 45 28 49 8b 84 24 d8 54 0c 00 49 8b 77 18 48 8b 90 10 58 02 00 <0f> b6 86 89 00 00 00 48 8b bc c2 50 04 00 00 e8 18 1a 2e 00 8b 45
Jan 27 17:28:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jan 27 17:29:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jan 27 17:30:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jan 27 17:31:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jan 27 17:32:10 localhost chronyd[854]: Selected source 188.125.64.7
Jan 27 17:32:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jan 27 17:33:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jan 27 17:34:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Jan 27 17:35:14 localhost journal[479258]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Cannot invoke method; proxy is for the well-known name org.gnome.Shell without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag

Machine boots but graphics are 800x600 resolution.

Card is:

01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [NVS 310] (rev a1)

I think it’s the 390 driver.

My machine even not showed any graphics at all when i last time tried to use the proprietary driver (390 too).  If your card is so old that it isn’t supported by newer p. drivers from vendor – give up and use nouveau.

My: GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1)

Which version of the nvidia drivers are you using. Did you get the one from nvidia or from rpmfusion?

Often the one from nvidia will have a problem with kernel updates, while rpmfusion tries to provide newly compiled versions that are made for the updated kernel.
Another difference is that if you have the rpmfusion repo enabled then the new versions are updated to match the kernel (almost) as quick as the kernel is updated while the nvidia versions are not quickly matched.

You can go to https://rpmfusion.org/Howto/NVIDIA and see how to update the drivers and verify which driver version is needed for your card by looking at the compatibility list. I checked there and found the NVS 310 is supported, and the latest driver is 390.132.

When I do a dnf install for the 390 driver as follows (of course I do not allow it to complete because my system uses the 440 driver) it returns

[QUOTE]# dnf install ‘nvidia-390xx’ --allowerasing
Last metadata expiration check: 2:12:49 ago on Fri 31 Jan 2020 08:49:54 AM MST.
Dependencies resolved.

Package Architecture Version Repository Size

Installing:
akmod-nvidia-390xx x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 25 k
kmod-nvidia-390xx x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 9.9 k
xorg-x11-drv-nvidia-390xx x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 2.7 M
xorg-x11-drv-nvidia-390xx-cuda x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 311 k
xorg-x11-drv-nvidia-390xx-cuda-libs x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 21 M
xorg-x11-drv-nvidia-390xx-devel x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 72 k
xorg-x11-drv-nvidia-390xx-kmodsrc x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 8.2 M
Installing dependencies:
nvidia-settings-390xx x86_64 390.132-1.fc31 rpmfusion-nonfree-updates 1.8 M
xorg-x11-drv-nvidia-390xx-libs x86_64 3:390.132-1.fc31 rpmfusion-nonfree-updates 15 M

Transaction Summary

Install 9 Packages
[/QUOTE]

Yours may be different, but this provides the proper version for the current kernel as well as the most recent driver update.