Thank you for the bug report. Judging by the DpkgLog.txt the upgrade that triggered your issue seems to include:
linux-firmware:all 20220329.git681281e4-0ubuntu3.35 20220329.git681281e4-0ubuntu3.36 linux-generic:amd64 5.15.0.125.124 5.15.0.126.125 linux-image-generic:amd64 5.15.0.125.124 5.15.0.126.125 linux-headers-generic:amd64 5.15.0.125.124 5.15.0.126.125 ubuntu-core-launcher:amd64 2.65.3+22.04 2.66.1+22.04 snapd:amd64 2.65.3+22.04 2.66.1+22.04 alsa-ucm-conf:all 1.2.6.3-1ubuntu1.11 1.2.6.3-1ubuntu1.12 gnome-control-center-data:all 1:41.7-0ubuntu0.22.04.8 1:41.7-0ubuntu0.22.04.9 gnome-control-center:amd64 1:41.7-0ubuntu0.22.04.8 1:41.7-0ubuntu0.22.04.9 gnome-control-center-faces:all 1:41.7-0ubuntu0.22.04.8 1:41.7-0ubuntu0.22.04.9 gnome-shell-extension-ubuntu-dock:all 72~ubuntu5.22.04.2.1 72~ubuntu5.22.04.3 lintian:all 2.114.0ubuntu1.4 2.114.0ubuntu1.5 linux-libc-dev:amd64 5.15.0-125.135 5.15.0-126.136 linux-tools-common:all 5.15.0-125.135 5.15.0-126.136 sosreport:amd64 4.5.6-0ubuntu1~22.04.2 4.7.2-0ubuntu1~22.04.1 teamviewer:amd64 15.58.4 15.60.3 sssd:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 python3-sss:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-proxy:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-krb5:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-ad:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-ldap:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-ipa:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-krb5-common:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-ad-common:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 sssd-common:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 libnss-sss:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 libpam-sss:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 libsss-certmap0:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 libsss-nss-idmap0:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 libsss-idmap0:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 libipa-hbac0:amd64 2.6.3-1ubuntu3.3 2.6.3-1ubuntu3.4 The highest suspect packages there would be sssd or the kernel. But we need more information to debug the issue. Are you able to provide a journal file? Boot the machine, reproduce the issue, switch virtual console, run: journalctl -b0 > journal.txt and attach the file here. Then, if you suspect this is an issue with the display manager, you could try starting a desktop session from the terminal with: XDG_SESSION_TYPE=wayland dbus-run-session gnome-session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2090805 Title: gdm blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2090805/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
