Thanks for your suggestions. Since I don't have a GUI, sending you a copy of the boot journal and attaching it to this ticket is a bit of a pain and I've been busy with work.
A bunch of points: 1. My boot sequence is messed up. I no longer see a grub boot menu so I can choose alternative boot options like old kernels or recovery mode. I tried to change /ec/default/grub to include GRUB_TIMEOUT_STYLE=countdown GRUB_TIMEOUT=3 and When I first rebooted after the initial broken package update, a whole bunch of red errors scrolled by too fast to see. It took me a while to think of trying to use the Ctl-Alt-F2 virtual console so by the time I did, its dmesg history file was gone. Those large groups of red-highlighted errors only were displayed the first time. 2, When I boot now, I do see some text after some point, There's a long wait after Starting systemd=networkd-wait-onl ait for Network to be configured a bunch of lines with ....12c 12c-3 , adapter quick: no zero length (addr 0x0018, size 0, wr for addr values of 12, 19, 1a, 29, 2a ,2b, 4c, 4d, 4e, 48 Job systemd-networkd-wait-online-service/start running (1min xxs/unlimited) It times out at 2min. I do seem to get an IP address, so I'm not sure what it's waiting and timing out on, or whether it's even relevant here. 3. While the sssd package is installed it's not actually configured to do anything (no /etc/sssd/sssd.conf file) I tried to set up an sssd.conf .file for LOCAL domain, but that just caused errors, so for now I've just disabled sss entries in /etc/nsswitch.conf (still keeping other entries like files and systemd) with no success. While it may not be fair, I'm more likely to blame snap. I've had no end of issues with snap locking firefox and chrome so that they won't startup, persistently across reboots. So with parts of gnome as snaps, I am more likely to be suspicious of snap, absent any reason to suspect anything else. I've just found it very unstable and had switched back to PPA deb package builds of the browsers to eliminate their hangs, and the apps had been rock-steady since. Though it is challenging to run a browser without a gui. lynx doesn't quite cut it. Thanks for your suggestions so far and looking forward to what you make of this boot journal On Mon, Dec 2, 2024 at 9:20 AM Alessandro Astone <2090...@bugs.launchpad.net> wrote: > 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 subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2090805 > > Title: > gdm blank screen > > Status in xorg package in Ubuntu: > New > > Bug description: > After applying updates, Ubuntu 22.04 suggested rebooting the system. > After rebooting the system, the GUI doesn't come up. It also seems to > have changed grub defaults so that the grub menu no longer displays > for a countdown of 3 seconds. > > During the first reboot after the update, a whole bunch of errors in > red flashed by as part of the boot sequence but I wasn't able to > capture them. That led to a non-responsive black screen with no > cursor. Then I tried a couple of more reboots, but while I didn't see > any red text, the system still didn't put up a GUI. > > I tried a few things that didn't work. I then tried to do a do- > release-upgrade to Ubuntu 24.04 that I had been putting of because I > couldn't afford the risk of downtime if the upgrade went badly in case > it fixed whatever config snafu the first package-level upgrade screwed > up. I also tried to do a package reinstall of the ubuntu-desktop, gdm, > and gnome packages and none of that work, although I did get a cursor > on a black screen at one point, so I think the compositor is working, > but the display manager isn't working. > > I can run commands on the Ctl-Alt-F2 virtual console, which is how I > initiated this bug report, but that's it. As far as I know, I'm > running gnome with the Wayland compositor. > > There were a bunch of apparmor messages and warnings at one point, so > I'm not sure if that could be the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 24.04 > Package: xorg 1:7.7+23ubuntu3 > ProcVersionSignature: Ubuntu 6.8.0-49.49-generic 6.8.12 > Uname: Linux 6.8.0-49-generic x86_64 > ApportVersion: 2.28.1-0ubuntu3.1 > Architecture: amd64 > CasperMD5CheckResult: pass > CloudArchitecture: x86_64 > CloudID: none > CloudName: none > CloudPlatform: none > CloudSubPlatform: config > Date: Sun Dec 1 18:25:25 2024 > DistUpgraded: 2024-12-01 15:33:41,183 DEBUG migrateToDeb822Sources() > DistroCodename: noble > DistroVariant: ubuntu > GpuHangFrequency: Continuously > GpuHangReproducibility: Yes, I can easily reproduce it > GpuHangStarted: Today > GraphicsCard: > Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 > XT/6750 XT / 6800M/6850M XT] [1002:73df] (rev c5) (prog-if 00 [VGA > controller]) > Subsystem: ASRock Incorporation Navi 22 [Radeon RX 6700/6700 XT/6750 > XT / 6800M/6850M XT] [1849:5210] > InstallationDate: Installed on 2020-12-21 (1441 days ago) > InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release > amd64 (20200731) > MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. > ProcEnviron: > LANG=C.UTF-8 > PATH=(custom, no user) > SHELL=/bin/bash > TERM=linux > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-49-generic > root=/dev/mapper/libbiegu-lv--root ro > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to noble on 2024-12-01 (0 days ago) > dmi.bios.date: 10/29/2020 > dmi.bios.release: 5.17 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: P1.10 > dmi.board.name: B550 Taichi Razer Edition > dmi.board.vendor: ASRock > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: To Be Filled By O.E.M. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550TaichiRazerEdition:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: To Be Filled By O.E.M. > dmi.product.sku: To Be Filled By O.E.M. > dmi.product.version: To Be Filled By O.E.M. > dmi.sys.vendor: To Be Filled By O.E.M. > mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07 > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.120-2build1 > version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2 > version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20210115-1build1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.17-2build1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2090805/+subscriptions > > ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/2090805/+attachment/5842046/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
