Lightdm shall never suspend the system itself. Instead it should properly report idle status to systemd where a decision can be taken by checking all relevant services, sessions and inhibitors.
In the past I have reported that idle suspend does not work while showing login screen: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606 After upgrade to 20.4 the system keeps suspending when one seat is showing login screen despite of a user is typing on another seat. The workaround here seems to help with the unwanted suspend, and still needs the cron job to override the missing idle hint and to suspend when applicable. Another similar reports mentioning multiseat setup as a victim of the gdm not playing in the team with systemd: https://gitlab.gnome.org/GNOME /gnome-control-center/-/issues/22 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #22 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1928305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
