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 1729296 - Automatic logout function logs out of GDM session, causing GUI to fail [rhel-7.9.z]
Summary: Automatic logout function logs out of GDM session, causing GUI to fail [rhel-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-settings-daemon
Version: 7.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Benjamin Berg
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1789022 2018606
TreeView+ depends on / blocked
 
Reported: 2019-07-11 19:36 UTC by Andrew Mike
Modified: 2024-03-25 15:21 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2018606 (view as bug list)
Environment:
Last Closed: 2020-12-15 11:11:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-settings-daemon merge_requests 205 0 None None None 2020-10-15 14:30:17 UTC
Red Hat Knowledge Base (Solution) 4279501 0 Troubleshoot None Why does the login screen show an "Automatic logout" message when no one is logged in? 2019-07-11 19:39:17 UTC
Red Hat Product Errata RHBA-2020:5436 0 None None None 2020-12-15 11:11:33 UTC

Description Andrew Mike 2019-07-11 19:36:59 UTC
Description of problem: When automatic logout dconf keys are set, the GDM session is logged out as well when the timeout is reached. This causes the GUI to fail and the display

Version-Release number of selected component (if applicable):
3.28.1-2

How reproducible: 100%


Steps to Reproduce:
1. Create /etc/dconf/db/local.d/10-logout with the following lines:
==============================================================
[org/gnome/settings-daemon/plugins/power]
sleep-inactive-ac-timeout=90
sleep-inactive-ac-type='logout'
==============================================================

2. Run "dconf reload" to reload the dconf database.
3. Get to the GDM login screen, either by logging out of a current GUI session or starting a new one with "systemctl isolate graphical.target".

Actual results: GDM session will be logged out after the timeout period passes with no input and the GUI will terminate, leaving a blank screen at the console.


Expected results: GDM will not log out after the timeout period passes without input; the logout function will apply only to logged-in sessions of GNOME.

Additional info: Cycling to multi-user mode then back to graphical mode will bring the login screen back, as will restarting the gdm service with systemctl. This may cause the GDM greeter to be started on another terminal.

This happens both on VMs and physical machines, but due to bug 1672998 the former needs to be started with "gnome.is_vm=0" on the command line for the automatic logout dconf keys to be honored.

Comment 7 Daniel Whitley 2019-12-20 18:11:01 UTC
I have reproduced the behavior (BUG) seen in BZ 1729296 on the latest workstation versions (RHEL7.7 and RHEL8.1) as well as a beta version (RHEL7.8).  What is required to get this addressed?  

I also believe the "FutureFeature" keyword to not be appropriate for this bug because this functionally worked previously.


To reproduce, I performed the following:
~~~
cat <<EOF>> /etc/dconf/db/local.d/10-logout
[org/gnome/settings-daemon/plugins/power]
sleep-inactive-ac-timeout=90
sleep-inactive-ac-type='logout'
EOF

dconf update 

grubby --remove-args="rhgb quiet" --args="gnome.is_vm=0" --update-kernel $(grubby --default-kernel)
# ^because I'm testing on a VM^

reboot
~~~


Each version is effected by BZ 1729296.  While the RHEL7.x workstation systems result in a non-usable screen until GDM is manually restarted, the RHEL8.x version appears to restart GDM and ends back up at the login screen resulting in a never ending loop of restarting GDM if a system is left at the login screen...:

~~~
# RHEL7.7:
[root@rhel77 ~]# date; rpm -q gnome-settings-daemon redhat-release-workstation; dconf dump /org/gnome/settings-daemon/plugins/power/
Fri Dec 20 12:44:26 EST 2019
gnome-settings-daemon-3.28.1-4.el7.x86_64
redhat-release-workstation-7.7-9.el7.x86_64
[/]
sleep-inactive-ac-timeout=90
sleep-inactive-ac-type='logout'

# RHEL7.8beta:
[root@rhel78 ~]# date; rpm -q gnome-settings-daemon redhat-release-workstation; dconf dump /org/gnome/settings-daemon/plugins/power/
Fri Dec 20 12:20:47 EST 2019
gnome-settings-daemon-3.28.1-8.el7.x86_64
redhat-release-workstation-7.8-1.el7.x86_64
[/]
sleep-inactive-ac-timeout=90
sleep-inactive-ac-type='logout'

# RHEL8.1:
[root@rhel81 ~]# date; rpm -q gnome-settings-daemon redhat-release; dconf dump /org/gnome/settings-daemon/plugins/power/
Fri Dec 20 13:00:50 EST 2019
gnome-settings-daemon-3.32.0-4.el8.x86_64
redhat-release-8.1-3.3.el8.x86_64
[/]
sleep-inactive-ac-timeout=90
sleep-inactive-ac-type='logout'
~~~

Comment 8 Daniel Whitley 2020-03-26 16:23:49 UTC
After reading that "A lot of design went into improving the login and unlock experience in GNOME" 3.36 [1] and understanding that this was the version in Fedora 32beta [2], I hoped against hope that this BZ would be addressed in that version of Gnome.  While the behavior is slightly different than what is experienced in RHEL7 and RHEL8, configuring a workstation to autologout per the settings as "verified" and published [3], results in a system logging out/crashing regardless of whether someone is logged in or not [4].

Based on the fact that the behavior around "autologout" is different between different versions of RHEL (and now Fedora) [5], I have to believe that changes are being made.  Unfortunately, I'm not sure what package is effecting the behavior, but how do I request that this be investigated further when those other changes are made?  Any help/guidance would be greatly appreciated.  Thanks.
-Daniel

[1] Introducing GNOME 3.36: “Gresik”
    > https://help.gnome.org/misc/release-notes/3.36/
[2] Announcing the release of Fedora 32 Beta
    > https://fedoramagazine.org/announcing-the-release-of-fedora-32-beta/
[3] How to enable user Auto Login and Logout in GUI mode on RHEL7 ?
    > https://access.redhat.com/solutions/1756193
[4] Why does the login screen show an "Automatic logout" message when no one is logged in and then GUI crash?
    > https://access.redhat.com/solutions/4279501
[5] when the configuration outlined in Comment #7 are in place, I see the following behavior (when no one is logged in):
    RHEL7: the login page crashes after sleep-inactive-ac-timeout is reached.  no recovery possible, but switching to a
           different VT allows for a user to log in at command line
    RHEL8: the login page crashes after sleep-inactive-ac-timeout is reached, appearing to restart GDM.  this results in
           an infinite loop of restarting GDM when no one is logged into a workstation and is therefore useless
    F32b:  the login page crashes after sleep-inactive-ac-timeout is reached, but results in a black screen with a
           blinking cursor in upper left corner.  if I simply switch to an alternate VT, and back, GDM appears to
           restart...

Comment 17 Daniel Whitley 2020-10-01 12:51:52 UTC
Since Red Hat Enterprise Linux 7.9 was released yesterday I thought I would attempt these settings in the latest RHEL7 version.  This OS version uses the same gnome-settings-daemon package version as RHEL7.8 and so, unsurprisingly, the behavior is the same...the logout method is invoked even when no user is logged in.

~~~
[root@rhel79 ~]# date; rpm -q gnome-settings-daemon redhat-release-workstation; dconf dump /org/gnome/settings-daemon/plugins/power/
Thu Oct  1 08:39:40 EDT 2020
gnome-settings-daemon-3.28.1-8.el7.x86_64
redhat-release-workstation-7.9-3.el7.x86_64
[/]
sleep-inactive-ac-timeout=90
sleep-inactive-ac-type='logout'
~~~

This is nothing more than my attempt at thoroughness.

Comment 20 Benjamin Berg 2020-10-15 14:30:29 UTC
OK, posted a relevant patch upstream that will fix it. From my side it is OK to backport this into 7.9. It is really simple and merged upstream already.

Comment 32 errata-xmlrpc 2020-12-15 11:11:21 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 (gnome-settings-daemon bug fix and enhancement update), 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-2020:5436


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