Created attachment 783827 [details]
After upgrade to x11-drivers/nvidia-drivers-510.73.05-r1 GDM hangs (black console terminal with _ symbol at top-left conner) with default configuration.
Looking to /lib/udev/rules.d/61-gdm.rules I found that Wayland session is enabled now with 510+ drivers, however it doesn't works for me out of the box.
There is not useful messages in journal as I see.
Created attachment 783830 [details]
journalctl --since today (unrelated network etc info cleaned)
Maybe bug 832861?
A few notes:
1. I have those GLib asserts in both wayland and X11 sessions.
2. Explicitly disabled Wayland session in GDM's custom.conf works for me on 510.
For nvidia bits, log is essentially saying that nothing went wrong from what I can see, so hard to say.
I did try gdm with 510 in stable before stabilizing and it worked fine here (with wayland, gentoo-kernel-bin-5.15.41 or so, no configuration using out-of-the-box settings).
Could possibly be hardware specific, but I'm not aware of any issues atm given normally gdm auto-disables wayland when it's not working regardless of the udev rules (e.g. for some dual card setups), but otherwise do use it even with nvidia if USE=wayland on nvidia-drivers.
510 does introduce major changes in that it supports GBM now, which cause certain applications to behave differently (formerly caused a lot more problems, but gnome/kde been rolling out fixes for this). e.g. applications which didn't try to use wayland with 470 may suddenly try to with 510, or use GBM instead of EGLStream (which gnome used to use for wayland with 470).
I just started to debug it today after world update but found it works now for unknown reason.
(In reply to nE0sIghT from comment #6)
> I just started to debug it today after world update but found it works now
> for unknown reason.
Strange, but glad to hear it works. Thanks for the update.