nvidia-drivers update crashes my machine

[jesnow]

Hi folks:

It's nice that nvidia have a rapid development cycle for their proprietary drivers, which have been running really well compared to the old days.

My problem is, about half the time, the version change causes my running system to crash, interrupting the emerge -DNua world. That makes me unhappy and I say bad words.

Is there some way to have portage defer upgrades to nvidia-drivers and simply issue a warning "please update nvidia-drivers". Kind of like the way portage does for itself. Or better yet, refuse to even start the emerge until nvidia-drivers is taken care of. "*** Warning: running video driver 'x11-drivers/nvidia-drivers-525.89.02' is scheduled for emerge. This might cause a system crash. It might be best to update it manually and restart. Continue? (y/n)"

Is there some way to make this part of the ebuild?

Cheers,

Jon.

[stefan11111]

Don't know about that, but you can mask all the versions above a known stable one and only emerge the drivers when you know that they won't break something.
_________________
My overlay: https://github.com/stefan11111/stefan_overlay
INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd /usr/lib/modules-load.d *udev* /usr/lib/tmpfiles.d *tmpfiles* /var/lib/dbus /usr/bin/gdbus /lib/udev"

[Ionen]

You can always --exclude nvidia-drivers so it'll be skipped if it shows up without needing mask, then could update it at same time as kernel or so allowing it to be updated fairly regularly still yet not out of the blue.

Most cases updating nvidia-drivers just render new GL/vulkan-using applications unable to start without currently running stuff breaking (so have time to finish things before reboot, it's just a bit annoying), but think some DEs (and depending on settings, haven't experimented much) may react poorly if they load new things using the new libraries and freeze entirely, guess it's what happening to you.