Gnome does not open (appear)

[Yosha872]

Since latest update, on 2023-01-09 my laptop can not reach Gnome, stuck on the text boot screen after GRUB. Kernel: 5.19.0-28 (previous installed was 5.19.0-26). No useful error message displayed.

When doing ALT+CTRL+F2 I can log as user and see (top) that the computer is not hang.
When doing CTRL+ALT+TAB, the graphical Ubuntu shutown screen does appear, then the computer does reboot.

When booting with 5.19.0-26 I can the same issue, but with more debug lines on the text boot screen. No useful error message displayed.

OS: ubuntu 22.10.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: plymouth 22.02.122-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
Uname: Linux 5.19.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 10 16:03:39 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2022-05-03 (251 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth
 Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575G
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2017
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.32
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 2.30
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32:
dmi.product.family: KBL
dmi.product.name: Aspire E5-575G
dmi.product.sku: Aspire E5-575G_115F_1.32
dmi.product.version: V1.32
dmi.sys.vendor: Acer

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please check for crashes and also collect a full system log:

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.

3. Run:
    journalctl -b0 > journal.txt
   and attach the resulting text file here.

[Yosha872 (yosha)]

1. Upload denied.
2. Issue reported at: https://errors.ubuntu.com/oops/69bf6a6e-9198-11ed-ab0f-fa163e55efd0
3. File attached.

[Daniel van Vugt (vanvugt)]

Thanks. That is bug 1717878.

[Yosha872 (yosha)]

Ok thanks. Note about the bug: my Gnome had login's password disabled, once GDM3 reinstalled, user password is now asked to login.

Below is how I have back my laptop without having to reinstall the whole OS (to help other users):
sudo apt remove gdm3
sudo apt purge gdm3
sudo apt install gdm3
reboot

[Daniel van Vugt (vanvugt)]

"purge" includes "remove" so you don't need the remove command. Although it's best to never tell people to remove core components because doing so can automatically trigger removing other core components. Which can end badly.

Maybe just try:

  sudo apt --purge reinstall gdm3