With =x11-drivers/nvidia-drivers-545.29.02 I have observed a crash that pretty reliably happens within a few minutes of login, though I have no clear idea of how exactly to explicitly force the crash to occur and it tends to occur when there is no keyboard or mouse input (hardware: 1060 notebook series) - a gnome crash screen appears and prompts me to log out. I have not observed the issue after installing =x11-drivers/nvidia-drivers-535.129.03 It is possible that the crash is more frequent (and occurs more quickly after login) with =x11-base/xorg-server-21.1.9, but I also observed it at least once when testing a downgrade to =x11-base/xorg-server-21.1.8-r2 Related discussion in archlinux forums suggests this may be more widespread: https://bbs.archlinux.org/viewtopic.php?id=290059 Reproducible: Always Steps to Reproduce: 1. Ensure =x11-drivers/nvidia-drivers-545.29.02 is installed, with hardware notebook series 1060 (possibly affects more hardware than this) as well as gnome and gnome dependencies 2. Boot and log in 3. Wait up to ~5 minutes or so Actual Results: Gnome crash, and coredumpctl reports a dump present for /usr/bin/gnome-shell Expected Results: No crash The following appears at the timestamp of the crash in the systemd journal: Received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 30730 error_code 2 request_code 139 (RANDR) minor_code 13) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the MUTTER_SYNC environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the mtk_x_error() function.)
> I have not observed the issue after installing =x11-drivers/nvidia-drivers-535.129.03 And to clarify, I have not observed the crash after downgrading and masking =x11-drivers/nvidia-drivers-545*
May want to try (just added) 545.29.06 to see if it helps. fwiw I have not heard of anyone else having this issue on Gentoo. Either way, not much can do about it given doubt it's a packaging issue and can't do much with semi-closed sources libraries. Better off reporting to nvidia and/or gnome. When something is very broken for a lot of people we may mask bad versions at most but does not seem to be the case here. Note that (new feature branch) 545 is never due to be stabled, stable will wait for the next production branch. Nothing wrong with sticking with a production branch (like stable 535, which will keep being supported for a long time still) if NFB cause problems for you.
