Bug 1956450
| Summary: | Unable to login to GNOME desktop on RHEL 8.4 RC | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Heesoon.Kim | ||||||||||||
| Component: | xorg-x11-server | Assignee: | Adam Jackson <ajax> | ||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 8.4 | CC: | hdegoede, lokanadham.dokku | ||||||||||||
| Target Milestone: | beta | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2022-03-08 12:14:09 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: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Heesoon.Kim
2021-05-03 17:44:35 UTC
Thanks for the report. Do you mind adding Enable=true to the [debug] section of /etc/gdm/custom.conf, reboot, reproduce, and then attach the full unfiltered output of # journactl -b > journal.txt to this bug? Can you describe in detail more about how the display gets messed? What sort of graphics hardware do you have installed? If you set WaylandEnable=false in the [daemon] section of /etc/gdm/custom.conf and reboot, does the problem still reproduce? We set WaylandEnable to false (uncommenting it) and it made no difference. We also use our own video card and setup so it might not be possible for you to reproduce. I currently loaded old gdm/pulseaudio package came with alpha on my system so I will update then attach journal.txt. Created attachment 1779081 [details]
journalctl -b output
Created attachment 1779086 [details]
journalctl -b output with a reboot
Thanks for the log. Can you describe how the display gets messed up? or provide a photo? On major change between the alpha and RC is a fix for this bug: * Wed Jan 27 2021 Ray Strode <rstrode> - 3.28.3-39• - Ensure login screen display server is is killed at log in• - Pull in fixes for two security issues• Resolves: #1918391• This makes sure that 10 seconds after login is started, the login screen X server is killed. Does the display start out okay, but then get messed up around 10 seconds later? It could be the driver used by the X server isn't handling getting killed in the background that well. Created attachment 1779090 [details]
video output -before and after login
After the reboot, everything functions. After the login (maybe 10 sec afterwards), display gets messed up (see attached word document) and not sure keyboard/mouse is working since display is messed up... Thanks. when this happens, if you send a ctrl-alt-f10 then ctrl-alt-f2 to the machine does that "repair" the corruption? Created attachment 1779100 [details]
before login
Created attachment 1779101 [details]
after login
One more thing that would be useful to know... If you go back to the GDM from the alpha, and after you log in, run: $ ps -ef |grep Xorg and get eg, gdm 778 772 0 15:09 tty1 00:00:05 /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -background none -noreset -keeptty -novtswitch -verbose 7 -core and find the Xorg background process associated with the login screen (the one running on tty1), then kill it from within the user session, e.g., # kill 778 does that also make the screen go garbled ? The key sequence ctrl/alt/f10 then ctrl/alt/f2 repairs the corruption. I can login as a root 2 times but the display gets messed up again on 3rd try. Also, repeated key sequences causes text mode prompt... Here is ps output from Alpha: [root@lin403 ~]# ps -ef |grep Xorg root 25429 25424 2 06:41 tty1 00:00:03 /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -background none -noreset -keeptty -novtswitch -verbose 3 root 26003 25999 10 06:42 tty3 00:00:05 /usr/libexec/Xorg vt3 -displayfd 3 -auth /run/user/0/gdm/Xauthority -background none -noreset -keeptty -novtswitch -verbose 3 root 26606 23915 0 06:43 pts/0 00:00:00 grep --color=auto Xorg If I kill 25429, the display gets messed up displaying black screen with blinking cursor. What version of the package xorg-x11-server-Xorg do you have? It seems like this fix: * Fri Jul 10 2020 Ray Strode <rstrode> - 1.20.8-4• - Don't switch VTs in the exit path, if killed on inactive VT• Related: #1618481• may not be working The package comes with 8.4.0-RC-1.0: [root@lin403 ~]# rpm -qa |grep xorg-x11-server-Xorg xorg-x11-server-Xorg-1.20.10-1.el8.x86_64 Any update? Looks like 8.4.0-GA version will be available tomorrow (is this still true?). Will this problem be fixed in GA? Any update on this bug? gdm/xorg problem is seriously affecting our rhel8 release. We are also seeing hot plugging issue with our VGA cards. Looks to be xorg problem: 571.208] (!!) More than one possible primary device found [ 571.208] (--) PCI: (44@0:0:0) 102b:0522:1bcf:804e rev 2, Mem @ 0x85000000/16777216, 0x84610000/16384, 0x86000000/8388608, BIOS @ 0x????????/65536 [ 571.208] (--) PCI: (102@0:0:0) 102b:0522:1bcf:804e rev 2, Mem @ 0x9f000000/16777216, 0xa0810000/16384, 0xa0000000/8388608, BIOS @ 0x????????/65536 Do you want us to enter another bug? We have root caused this problem and resolved this issue by providing a link to fb device after a failover. I am closing this issue. |