Bug 1043571 - Timed Login Failure
Summary: Timed Login Failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1064025
TreeView+ depends on / blocked
 
Reported: 2013-12-16 16:36 UTC by Michael Boisvert
Modified: 2019-04-16 14:06 UTC (History)
8 users (show)

Fixed In Version: gdm-3.8.4-30.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:20:53 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 680348 0 High RESOLVED Timed login is broken 2019-12-23 17:47:30 UTC
Red Hat Product Errata RHSA-2015:0535 0 normal SHIPPED_LIVE Low: GNOME Shell security, bug fix, and enhancement update 2015-03-05 16:32:34 UTC

Description Michael Boisvert 2013-12-16 16:36:40 UTC 
Description of problem:

I add following lines into:  /etc/gdm/custom.conf
          
          [daemon]
          TimedLoginEnable=true
          TimedLogin=$username
          TimedLoginDelay=30

How reproducible: Every log in besides the first after restarting the machine. 


Steps to Reproduce:
1. Create custom.conf with above information.
2. Log out/kill gdm
3. Wait.

Actual results: The progress bar under the username takes 30 seconds to complete, but it never actually logs into the account.

Expected results: Account logs in automatically after specified time.

Additional Info: It works as the first log in on the machine, but if you log out it tries again but never logs in.
Comment 5 Larry 2014-09-08 13:14:58 UTC 
I am seeing the same problem with the recently released production version of Red Hat Enterprise Linux 7.
Comment 10 Michael Boisvert 2015-01-23 15:25:59 UTC 
Timed login has worked in snap 2 and snap 4. Verified.
Comment 12 errata-xmlrpc 2015-03-05 13:20:53 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://rhn.redhat.com/errata/RHSA-2015-0535.html
Note You need to log in before you can comment on or make changes to this bug.