Key issues here.
Update went well, restart ok, but even cleaning keys, reinstalling them (after server check) I get numerous key errors like these ones:
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: public key DB323392796CA067 is 3037 days newer than the signature
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
I am having a similar problem on a Dell xps laptop. GDM starts but I never get the user selection window to log in. I get the top toolbar and can restart with the mouse. I can login via tty and startx which works.
Again after the Update my GUI did not show. I had to delete 2 Files in console (CTRL ALT F2). Then the next boot works again.
I did solve my problem. But i do think this is an Error “upstream” introduced by 2 configfiles with an Section “ServerLayout”. I think this will break every multiseat-setup using loginctl (like suggested in arch-wiki)
How do i inform the author of the files of the unwanted consequences of his work ?
Can now confirm the issue is because I was running the Pop Shell extension, which does not work in Gnome 40. Unfortunately, uninstalling the extension does not resolve the issue. If anyone has any suggestions as to how I can resolve this please let me know.
Applying the update I ran into no errors, but after a short time, I started to experience graphical glitches. The glitches happen when using the application overview our switching workspaces. This post has similar issues that I’m experiencing Graphical glitches in GNOME Overview after upgrading to Gnome 40 . I ended up reverting back to a timeshift backup. Going to give gnome 40 some more time before I move over since some of my extensions are still not compatible.
Upgrade went fine for me, nice to see the new Gnome fully in.
Given that this release includes the Nvidia 470 drivers and XWayland 21.1.2, it should now be possible to run a Wayland desktop with no performance penalties. Will stable users be switched over by default at some point? If not, is there a guide to manually switching to Wayland? I haven’t tried running it before.
I’m similarly curious about Pipewire, it sounds like it’s now stable enough to fully replace PulseAudio, but I’m not sure how to switch over. (Given that’s it’s the only way to stream one’s desktop/gaming in OBS with Wayland, I’d probably need to.)