Bug 1654446 - Timedlogin fails when userlist is disabled after upgrading from RHEL 7.5 to 7.6
Summary: Timedlogin fails when userlist is disabled after upgrading from RHEL 7.5 to 7.6
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.6
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
Depends On:
Blocks: 1668895
TreeView+ depends on / blocked
Reported: 2018-11-28 20:06 UTC by tfahl
Modified: 2021-02-13 07:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1668895 (view as bug list)
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description tfahl 2018-11-28 20:06:24 UTC
Description of problem:
After upgrading from RHEL 7.5 to 7.6 the TimedLogin option for gdm is no longer working. The error only occurs when the user list is disabled. With the user list enabled Timedlogin works for users on the user list. 

Version-Release number of selected component (if applicable):
RHEL 7.6 

How reproducible:
Always reproducible

Steps to Reproduce:
1. Setup the Timedlogin option in /etc/gdm/custom.conf

2. Add dconf settings to disable the userlist on the login screen
Create the file: /etc/dconf/db/gdm.d/00-login-screen and add these options:


Update dconf via 'dconf update'

3. Restart gdm via 'systemctl restart gdm.service'

Actual results:
The user never logs in

Expected results:
After a timeout of 10 seconds the specified user is logged in.

Additional info:

The following error can be seen in journalctl

gnome-shell[36678]: JS ERROR: Exception in callback for signal: release: TypeError: this._timedLoginItem is null                                              _showTimedLoginAnimation@resource:///org/gnome/shell/gdm/loginDialog.js:1003:9                                               wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                             run@resource:///org/gnome/shell/gdm/batch.js:64:20                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                             runTask@resource:///org/gnome/shell/gdm/batch.js:144:16                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                             process@resource:///org/gnome/shell/gdm/batch.js:210:19                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                              nextTask@resource:///org/gnome/shell/gdm/batch.js:161:9                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                             process@resource:///org/gnome/shell/gdm/batch.js:222:12                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                            nextTask@resource:///org/gnome/shell/gdm/batch.js:161:9                                              wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                             process/signalId<@resource:///org/gnome/shell/gdm/batch.js:217:16                                              _emit@resource:///org/gnome/gjs/modules/signals.js:128:27                                               release@resource:///org/gnome/shell/gdm/batch.js:102:13                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22                                          _blockTimedLoginUntilIdle/this._timedLoginIdleTimeOutId<@resource:///org/gnome/shell/gdm/loginDialog.js:1022:17

Comment 2 Bob Dingman 2019-06-28 13:12:30 UTC
I encountered this as well but had not discovered the dependence on the login-screen "disable-user-list=true" setting. Thank you for posting!

It was confusing because AutomaticLogin still works (i.e., with RHEL 7.6 with the login-screen "disable-user-list=true" setting.)

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