Bug 1689413

Summary:	gdm displays incorrectly on boot if machine is hooked to multiple monitors with differing resolution
Product:	Red Hat Enterprise Linux 8	Reporter:	Porygon <jsolomon>
Component:	mutter	Assignee:	Jonas Ådahl <jadahl>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	fmuellner, hdegoede, jkoten
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-01 07:39:34 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:

Description Porygon 2019-03-15 20:31:44 UTC

when booting machine initially, gdm will display incorrectly on a secondary monitor. Internal display/primary monitor will usually look fine, but on the secondary monitor there will be large graphical glitches. If the second monitor is higher resolution, half of the screen will often be blank with the login entry near the bottom; if the second monitor is lower resolution, there usually isn't blanking but the login prompt will be offset greatly and usually drawn offscreen.

Plymouth displays fine beforehand. gnome-shell also displays fine.

Version-Release number of selected component (if applicable):
RHEL-8.0.0-20190228.1
gdm-3.28.3-20.el8.x86_64

Steps to Reproduce: 
 1. Connect at least two displays with different max resolutions to the machine (internal displays affect this too)
 2. Boot the machine and wait for gdm to appear

Actual results: 

 1. gdm has significant graphical glitches on one monitor in dual-head mode (described at the top of report)

Expected results:
 1. gdm displays correctly on all connected displays

Additional info:
tested on T480s (Intel UHD Graphics 620) and a desktop machine with AMD Fiji (Radeon R9 FURY/NANO series)
with monitors Asus VP28UQG, Acer K242HQK, and Samsung SyncMaster 275T hooked up both directly and through dock in varying combinations

Comment 1 Ray Strode [halfline] 2019-06-17 17:40:05 UTC

fixing component

does disabling wayland in /etc/gdm/custom.conf help?

Comment 2 Porygon 2019-08-06 00:30:29 UTC

Hi, sorry for the late response to this. It does appear that disabling Wayland causes the issue to go away.

Comment 4 Jonas Ådahl 2020-02-21 16:53:07 UTC

Some questions:

Is this still an issue with 8.1? The display server used by gdm was upgraded betwene 8.0 and 8.1 with many bug fixes coming with it.

Without having disabled wayland in gdm.conf, after you log in to the session, are you selecting the default session, or X11 one?

If you log out, is gdm still showing up incorrectly?

Comment 9 RHEL Program Management 2021-02-01 07:39:34 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.