Bug 1998989

Summary: [RHEL8.5] [Hyper-V]Cannot display GUI after installed RHEL8.5 recent build
Product: Red Hat Enterprise Linux 8 Reporter: xxiong
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: xxiong
Severity: high Docs Contact:
Priority: high    
Version: 8.5CC: cavery, hdegoede, huzhao, litian, lmiksik, mmorsy, ribarry, rstrode, tpelka, vkuznets, xuli, xxiong, yacao, yuxisun
Target Milestone: rcKeywords: Regression, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gdm-40.0-13.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2000904 (view as bug list) Environment:
Last Closed: 2021-11-09 19:34:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2000904    
Attachments:
Description Flags
log after enabled debug none

Description xxiong 2021-08-30 07:49:17 UTC
Created attachment 1818992 [details]
log after enabled debug

Created attachment 1818992 [details]
log after enabled debug

Created attachment 1818992 [details]
log after enabled debug

Created attachment 1818992 [details]
log after enabled debug

Description of problem:

VM will display black after installed RHEL8.5 and click the FINISH CONFIGURATION button on the last step

Version-Release number of selected component (if applicable):

Host: 
Hyper-V 2019

Guest: 
occurs since RHEL-8.5.0-20210824.n.1-x86_64

4.18.0-335.el8.x86_64
gdm-40.0-12.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create an new VM with GEN1 or GEN2 option
2. Load the RHEL ISO file on DVD
3. Start VM and check the display on console
4. Click 'Reboot' button
5. Click the 'FINISH CONFIGURATION' button and check the result

Actual results:
1. The VM  installation well until step 5
2. The VM console will display black after step 5
3. GUI will display well after 
setting WaylandEnable=false in the [daemon] section of /etc/gdm/custom.conf, and reboot 
4  This not occurs on RHEL-8.5.0-20210816.n.0-x86_64(kernel:4.18.0-330.el8.x86_64/gdm-40.0-3.el8.x86_64)

Expected results:
1. The installation should work well and GUI display well after installed

Additional information:
Please check the attachment.

Additional info:
this issue will not occurs after yum installed the 
gdm-40.0-3.el8.x86_64

Comment 15 xxiong 2021-09-02 08:09:22 UTC
Hi Ray,

I attached the output of 'udevadm info --export-db' on both 'gdm-40.0-12.el8.x86_64' and 'gdm-40.0-13.el8.x86_64'.

1.Checked with gdm-40.0-13.el8.x86_64, GUI can display and login, but the item changed in the gear on login page (screenshot attached): "Standard(X11 as display server) on Xorg" --> "Standard(X11 as display server)", is this change expected?

2.Checked with the script of comment 8, the cli result as below:

a>
\n\n\nChecking if Xorg fallback worked-: OK
test-fallback.sh: line 62: 11029 Terminated              journalctl -f -n0
wayland x11
[root@vm-198-172 ~]# rpm -q gdm
gdm-40.0-13.el8.x86_64

GUI will create a new user:  test-fallback-session-user, but gui user list will disappear a while after clicking the 'test-fallback-session-user', then GUI will display the user selection page again, is this the script expected result?

b>
\n\n\nChecking if Xorg fallback worked-: FAILED
md5sum: WARNING: 1 computed checksum did NOT match
test-fallback.sh: line 62: 78354 Terminated              journalctl -f -n0
wayland wayland
[root@bootp-73-199-210 ~]# rpm -q gdm
gdm-40.0-12.el8.x86_64

The bug issue appeared, GUI disappeared, even it was configured: WaylandEnable=false in the [daemon] section of /etc/gdm/custom.conf

3. About comment 10: 
"I'd like to add a udev rule to force hyperv to go straight to xorg rather than relying on fallback.  It should speed up boot and side step this class of bugs for the future."

It only needs on RHEL8, but not RHEL9, since on RHEL9, it supported wayland (https://bugzilla.redhat.com/show_bug.cgi?id=1972122), right?

If so, will the rule still take effect when upgrading from RHEL8 to RHEL9?

Thanks

Comment 16 Ray Strode [halfline] 2021-09-02 10:21:53 UTC
1. is a change in gnome-session from bug 1962211 . it's not directly related to this gdm build. i guess you probably upgraded gnome-session at the same time when installing the new package.
2. yes that's expected. when the script is running it does auto login to an dummy session that's just a black screen.  When the script is finished it returns to the login screen.

The important part of the script is "Checking if Xorg fallback worked-: OK" .  Of course the script was just to illustrate how it could potentially be tested in GDMs CI tests. The important thing is that HyperV works...

3. That's right, the udev rule ships with GDM so it will go away in RHEL 9 when GDM is upgraded.

Comment 17 Ray Strode [halfline] 2021-09-02 10:31:07 UTC
okay i've got a scratch build going that should disable wayland on HyperV too: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=39499317

Comment 24 xxiong 2021-09-06 04:17:28 UTC
Checked on compose: RHEL-8.5.0-20210906.n.0-x86_64 (kernel: 4.18.0-339.el8.x86_64, gdm: gdm-40.0-13.el8.x86_64)

1. Now the GUI installation works well with GEN1 and GEN2

2. Also checked login with each display server, GUI login and display well
-Standard(X11 display server)
-Classic(X11 display server)
-Custom
-User script

3.Run the script of comment 8:
GEN1:
\n\n\nChecking if Xorg fallback worked-: OK
test-fallback.sh: line 62: 15623 Terminated              journalctl -f -n0
wayland x11

GEN2:
\n\n\nChecking if Xorg fallback worked-: OK
test-fallback.sh: line 62: 14197 Terminated              journalctl -f -n0
wayland x11

Comment 26 errata-xmlrpc 2021-11-09 19:34:51 UTC
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.

https://access.redhat.com/errata/RHSA-2021:4381