Bug 1687952

Summary:	gdm login does not respond to keyboard input if monitor is not connected
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:	cgarnach, fmuellner, hdegoede
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
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:25 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-12 18:20:55 UTC

Test for logging into a gnome-shell session on a headless machine currently fails.

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

Steps to Reproduce: 
 1. Use a machine with no monitor currently attached
 2. Boot the machine and wait until boot finishes
 3. Press Enter
 4. Blind-type password and hit enter again
 5. Wait a moment for login to finish
 6. Connect a monitor

Actual results: 

 1. Monitor turns on when reconnected, user is not logged in and monitor displays gdm login screen

Expected results:

 1. Monitor turns on when reconnected, user is logged in and monitor displays logged in gnome-shell session

Additional Details:
Monitor connected to Fiji Radeon R9 FURY/NANO through DisplayPort

Comment 1 Jonas Ådahl 2019-03-13 08:15:23 UTC

I suppose this is due to input events being tied to the frame clock. Without a monitor connected, there'll be no frames, so no events.

Comment 4 RHEL Program Management 2021-02-01 07:39:25 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.