Good morning wonderful people,
System info:
user@host:~# cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.3 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
user@host:~# gnome-shell --version
GNOME Shell 46.0
user@host:~# gdm3 --version
GDM 46.2
I’m seeking guidance on the intended behavior of GDM when managing multiple graphical sessions on a single machine’s seat0. I run a computer lab with many students taking computer science courses on the same machines. Frequently, my userbase does not logout of their own decision when the class session concludes.
My goal is to have multiple users logged into separate gnome-shells (e.g. tty2 and tty3) where I have an automatic logout based on inactivity where the idle user on tty2’s automatic logout does not prompt the seat to return to GDM and the physical console to return to tty1 (thus disrupting the logged in gnome-shell on tty3). My primary reason for a graceful logout is to ensure applications like Firefox and Google Chrome clean up their application specific lock files before the session ends (see my chromium issue report for exact details).
I followed the autologout procedure to automatically ‘logout’ idle users after 30 minutes of idle. I assume what this dconf setting does it run gnome-session-quit --logout --no-prompt or something similar for the user after the idle timeout.
I tried creating a systemd script with loginctl as well, but I’m starting to think this is a constraint based on how GDM was implemented.
Thanks for any advice!
Kevin