On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries

What is the behavior when you try to log in? Do you get an authentication failure message, or does it appear there is a successful login followed by a screen flicker and a return to the login screen?

Are there failure messages in /var/log/auth.log?

There is some funky stuff going on in auth.log.

I go to log in, enter my password, it starts the process, then lands me back at the gdm login screen after a second.

2023-10-14T01:44:00.468542-04:00 anadon gdm-password]: pam_unix(gdm-password:session): session opened for user anadon(uid=1000) by (uid=0)
2023-10-14T01:44:00.473683-04:00 anadon systemd-logind[1169]: New session 6 of user anadon.
2023-10-14T01:44:00.522860-04:00 anadon (systemd): pam_unix(systemd-user:session): session opened for user anadon(uid=1000) by (uid=0)
2023-10-14T01:44:00.658692-04:00 anadon gdm-password]: gkr-pam: unlocked login keyring
2023-10-14T01:44:01.673108-04:00 anadon gnome-keyring-daemon[3237]: The PKCS#11 component was already initialized
2023-10-14T01:44:01.673392-04:00 anadon gnome-keyring-daemon[3560]: discover_other_daemon: 1
2023-10-14T01:44:01.674538-04:00 anadon gnome-keyring-daemon[3237]: The Secret Service was already initialized
2023-10-14T01:44:01.674742-04:00 anadon gnome-keyring-daemon[3562]: discover_other_daemon: 1
2023-10-14T01:44:01.677463-04:00 anadon gnome-keyring-daemon[3563]: discover_other_daemon: 1
2023-10-14T01:44:09.242277-04:00 anadon PackageKit: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
2023-10-14T01:44:09.243637-04:00 anadon PackageKit: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
2023-10-14T01:44:10.632860-04:00 anadon gdm-password]: pam_unix(gdm-password:session): session closed for user anadon
2023-10-14T01:44:10.643754-04:00 anadon systemd-logind[1169]: Session 6 logged out. Waiting for processes to exit.
2023-10-14T01:44:10.644366-04:00 anadon systemd-logind[1169]: Removed session 6.

This appears to show a successful login with gdm. So if launching the graphical session fails afterwards, that must be an issue with gdm or some other downstream component. Reassigning.

The journal shows a gnome-shell error

Bail out! Gjs:ERROR:../gi/wrapperutils.h:847:static Prototype* GIWrapperPrototype<Base, Prototype, Instance, Info>::create_prototype(Info*, GType) [with Base = InterfaceBase; Prototype = InterfacePrototype; Instance = InterfaceInstance; Info = _GIBaseInfoStub; GType = long unsigned int]: assertion failed: (gtype != G_TYPE_INVALID)

Do you have local extensions installed? Could you try if a new user has the same issue?

No local extensions are installed. Only the default system extensions <email address hidden> and <email address hidden> are installed following https://askubuntu.com/questions/1133782/command-to-list-installed-and-enabled-gnome-extensions. XFCE4 is now also broken so I'm without a GUI for the moment.

I did try with a blank new user and they have no such issues.

There's also a lot of this in the journal:

  GNOME Shell crashed with signal 11

so to help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Also just in case you've found a new form of bug 2034619 please try adding this to /etc/environment:

  MUTTER_DEBUG_KMS_THREAD_TYPE=user

and then reboot.