Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-20757

Idle session setting kills the GDM process

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • rhel-9.4
    • rhel-9.4
    • systemd
    • None
    • systemd-252-23.el9
    • sst_cs_plumbers
    • ssg_core_services
    • 26
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • x86_64
    • None

      What were you trying to do that didn't work?

      The customer needs to configure StopIdleSessionSec in /etc/systemd/logind.conf, but it killing GDM leaving blank console with flashing underscore.

      How reproducible:
      Everytime

      =======================
      REPRODUCER
      =======================

      • Install RHEL8.9, select Workstation.

      ~~~
      cat /etc/redhat-release
      Red Hat Enterprise Linux release 8.9 (Ootpa)

      rpm -q systemd gdm
      systemd-239-78.el8.x86_64
      gdm-40.0-27.el8.x86_64
      ~~~

      • Add StopIdleSessionSec=100 to /etc/systemd/logind.conf:

      ~~~
      [root@localhost ~]# grep -v ^# /etc/systemd/logind.conf

      [Login]
      StopIdleSessionSec=100
      ~~~

      • Restart the service:

      ~~~
      ~]# systemctl restart systemd-logind
      ~~~

      • Login again with user and password. The console is black with a flashing underscore. But if I enter Ctrl+C, the login screen appears again and after enter user and password the login is successful.
        =======================

      Expected results

      Login screen should get locked after mentioned time.

      Actual results

      The console is black with a flashing underscore.

            systemd-maint systemd maint mailing list
            rhn-support-vikpatil Vikramsingh Patil
            Jan Pazdziora, Michal Sekletar
            systemd maint mailing list systemd maint mailing list
            Frantisek Sumsal Frantisek Sumsal
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: