Bug 1962049
| Summary: | [Hyper-V][RHEL8.5]gdm: Guest with 1 vcpu start GUI failed on Hyper-V | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | HuijingHei <hhei> | ||||
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED ERRATA | QA Contact: | HuijingHei <hhei> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.5 | CC: | hdegoede, hhei, huzhao, mboisver, xuli, yacao, yuxisun | ||||
| Target Milestone: | beta | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gdm-40.0-2.el8 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-11-09 19:34:38 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
HuijingHei
2021-05-19 09:02:40 UTC
can you set Enable=true in the [debug] section of /etc/gdm/custom.conf then reboot and attach the unfiltered output of journalctl -b to this bug? Created attachment 1784793 [details] gdm debug log Hi, attach logs according to comment #1 hmm, This looks related: May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com gdm[962]: Gdm: GdmManager: trying to register new display May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com gdm[962]: Gdm: GdmCommon: Found session c2 for PID 1641, using May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com gdm-x-session[1641]: Gdm: Could not register display: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No display available May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com /usr/libexec/gdm-x-session[1641]: Unable to register display with display manager So it's failing to register the display. I wonder if we're hitting a failure in fallback logic. Does putting WaylandEnable=false in the [daemon] section of /etc/gdm/custom.conf make things start working? ah I see the problem, the workaround I have in place until bug 1642460 is resolved got misapplied to the wrong branch of an if statement when I rebased GDM. (In reply to Ray Strode [halfline] from comment #3) > hmm, > > This looks related: > > May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com gdm[962]: Gdm: GdmManager: > trying to register new display > May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com gdm[962]: Gdm: GdmCommon: > Found session c2 for PID 1641, using > May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com gdm-x-session[1641]: Gdm: > Could not register display: > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No display available > May 19 19:27:25 vm-197-89.lab.eng.pek2.redhat.com > /usr/libexec/gdm-x-session[1641]: Unable to register display with display > manager > > So it's failing to register the display. I wonder if we're hitting a failure > in fallback logic. > > Does putting WaylandEnable=false in the [daemon] section of > /etc/gdm/custom.conf make things start working? GUI works well if add 'WaylandEnable=false' in the [daemon] section of /etc/gdm/custom.conf. Thanks! Can not reproduce the problem with gdm-40.0-2.el8.x86_64. Thanks for your quick fix! Verify passed with compose RHEL-8.5.0-20210521.n.1 ( with gdm-40.0-2.el8.x86_64 ), can not reproduce the problem 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 |