[Hyper-V][RHEL8] VM starts GUI failed on Hyper-V 2019/2016, hangs at "Started GNOME Display Manager" - GDM regression issue.
VM starts GUI failed on Hyper-V 2019/2016, hangs at "Started GNOME Display Manager". The issue exists on both Gen1 and Gen2 vm. Based on test, regression issue is caused by GDM package gdm-3.28.3-30.el8, if install back the gdm-3.28.3-29.el8, GUI can login successfully.
Version-Release number of selected components (if applicable):
Steps to Reproduce:
1. Install VM with RHEL8.3 compose RHEL-8.3.0-20200811.0 on Hyper-V, and install GUI packages
2. Start VM.
GUI displays failed, hangs at "Started GNOME Display Manager."
Start GUI normally
When the issue occurs, network and ssh work well. If install back gdm-3.28.3-29.el8.x86_64.rpm, gui can display well.
rpm -ivh http://download.eng.bos.redhat.com/brewroot/vol/rhel-8/packages/gdm/3.28.3/29.el8/x86_64/gdm-3.28.3-29.el8.x86_64.rpm --force
Aug 11 15:47:53 vm-198-143.lab.eng.pek2.redhat.com gnome-shell: unable to open file '/etc/dconf/db/gdm': Failed to open file “/etc/dconf/db/gdm”: open() failed: No such file or directory; expect degraded >
Aug 11 15:47:53 vm-198-143.lab.eng.pek2.redhat.com gnome-shell: Failed to create backend: No GPUs found with udev
Aug 11 15:47:53 vm-198-143.lab.eng.pek2.redhat.com systemd: NetworkManager-dispatcher.service: Succeeded.
Aug 11 15:47:53 vm-198-143.lab.eng.pek2.redhat.com gnome-session: gnome-session-binary: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 11 15:47:53 vm-198-143.lab.eng.pek2.redhat.com gnome-session-binary: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 11 15:47:53 vm-198-143.lab.eng.pek2.redhat.com gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop
Created attachment 1712790 [details]
journalctl -b log for comment 15 on Azure
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: GNOME security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.