RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1373837 - gdm not starting because of error in config
Summary: gdm not starting because of error in config
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1370511
TreeView+ depends on / blocked
 
Reported: 2016-09-07 08:55 UTC by Martin Krajnak
Modified: 2017-08-01 22:57 UTC (History)
5 users (show)

Fixed In Version: gdm-3.22.3-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:57:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 695250 0 None None None 2016-09-07 14:27:20 UTC
Red Hat Product Errata RHSA-2017:2128 0 normal SHIPPED_LIVE Moderate: gdm and gnome-session security, bug fix, and enhancement update 2017-08-01 19:38:38 UTC

Description Martin Krajnak 2016-09-07 08:55:54 UTC
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 14:27:21 UTC
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 14:42:20 UTC
(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 14:53:59 UTC
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 18:54:58 UTC
okay added the patch from the upstream bug.

Comment 6 Michael Boisvert 2017-05-25 15:12:35 UTC
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 22:57:55 UTC
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.