Bug 1373837 – gdm not starting because of error in config

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1373837 - gdm not starting because of error in config

Summary:	gdm not starting because of error in config

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	gdm (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	x86_64 Linux

Priority	unspecified Severity low
Target Milestone:	rc
Target Release:	---
Assigned To:	Ray Strode [halfline]
QA Contact:	Desktop QE
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1370511
	Show dependency tree / graph

Reported:	2016-09-07 04:55 EDT by Martin Krajnak
Modified:	2017-08-01 18:57 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	gdm-3.22.3-3.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-01 18:57:55 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
GNOME Bugzilla	695250	None	None	None	2016-09-07 10:27 EDT
Red Hat Product Errata	RHSA-2017:2128	normal	SHIPPED_LIVE	Moderate: gdm and gnome-session security, bug fix, and enhancement update	2017-08-01 15:38:38 EDT

Groups: None (edit)

Description Martin Krajnak 2016-09-07 04:55:54 EDT

Description of problem:
gdm was frozen right after start, because of misconfigured /etc/gdm/custom.conf where I had:

[daemon]
AutomaticLoginEnable = true
AutomaticLogin = test

There was no user named test in system. After commenting these lines everything solved the problem but gdm greeter should be shown despite the error in config and there should be no freezes.


Version-Release number of selected component (if applicable):
gdm-3.14.2-18.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. add user test
2. configure autologin
3. delete user test
4. restart system

Actual results:
System is frozen after gdm starts.

Expected results:
System should show gdm greeter screen or some error message without freezes.

Additional info:

Comment 1 Ray Strode [halfline] 2016-09-07 10:27:21 EDT

upstream bug has a patch, though, it also points out the patch is less than optimal.

We should probably fix this in 7.4 via rebase than in 7.3

Comment 2 Tomas Pelka 2016-09-07 10:42:20 EDT

(In reply to Ray Strode [halfline] from comment #1)
> upstream bug has a patch, though, it also points out the patch is less than
> optimal.
> 
> We should probably fix this in 7.4 via rebase than in 7.3

No one hit this issue except QE, so I guess it is save to fix in 7.4.

Comment 3 Ray Strode [halfline] 2016-09-07 10:53:59 EDT

right, it's not a regression or anything, i think it's been a problem since RHEL 3, but at least since RHEL 5.

We should fix it for 7.4 though.

Comment 4 Ray Strode [halfline] 2017-03-10 13:54:58 EST

okay added the patch from the upstream bug.

Comment 6 Michael Boisvert 2017-05-25 11:12:35 EDT

The solution is pretty good actually. The system automatically logs into a new basic GNOME session that gets your name/username/password during the initial setup. After you complete it, you are logged into your new account.

Comment 7 errata-xmlrpc 2017-08-01 18:57:55 EDT

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, 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-2017:2128

Note You need to log in before you can comment on or make changes to this bug.