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 1446762 - TimedLogin via custom.conf no longer working
Summary: TimedLogin via custom.conf no longer working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1456511
TreeView+ depends on / blocked
 
Reported: 2017-04-28 20:03 UTC by Michael Boisvert
Modified: 2017-08-01 22:44 UTC (History)
4 users (show)

Fixed In Version: gnome-shell-3.22.3-10.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:44:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
var/log/gdm files (108.87 KB, application/zip)
2017-06-06 18:53 UTC, Michael Boisvert
no flags Details
journalctl -ab (301.05 KB, text/x-vhdl)
2017-06-06 18:54 UTC, Michael Boisvert
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2098 0 normal SHIPPED_LIVE gnome-shell-extensions, gnome-shell, mutter bug fix and enhancement update 2017-08-01 19:36:42 UTC

Description Michael Boisvert 2017-04-28 20:03:01 UTC
Description of problem: Timed login via the custom.conf method is not working anymore. 

How reproducible: 100%

Steps to Reproduce:

1. Add following lines into file:  /etc/gdm/custom.conf
          [daemon]
          TimedLoginEnable=true
          TimedLogin=$username
          TimedLoginDelay=10
2. Run "systemctl restart gdm"

Actual results: The timed login progress bar never appears and the user is never automatically logged in after 10 second. 

Expected results: The specified user is automatically logged in after the specified 10 seconds.

Comment 3 Ray Strode [halfline] 2017-06-06 18:26:59 UTC
can you put Enable=true in the [debug] section of /etc/gdm/custom.conf and then reproduce and post the output of jouranctl -ba and the files in /var/log/gdm ?

Comment 4 Michael Boisvert 2017-06-06 18:53:15 UTC
Created attachment 1285513 [details]
var/log/gdm files

Comment 5 Michael Boisvert 2017-06-06 18:54:35 UTC
Created attachment 1285514 [details]
journalctl -ab

Comment 11 Michael Boisvert 2017-06-14 19:13:08 UTC
Timed login is now verified as working.

Comment 12 errata-xmlrpc 2017-08-01 22:44:12 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/RHBA-2017:2098


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