org.gnome.ScreenSaver.GetActive returns true under GDM even when typing into the login
Submitted by Iain
Link to original bug (#793185)
Description
(This may be the wrong component, but the behaviour is affecting the GDM account.)
I'm polling org.gnome.ScreenSaver.GetActive from a script launched under the GDM user, to see when our users are at the console of a PC but not yet logged in.
For the first five minutes after boot (the default screen timeout), this returns false. At five minutes, org.gnome.ScreenSaver.GetActive returns true, org.gnome.ScreenSaver.GetActiveTime starts counting from 0 and the screen dims then blanks.
If I move the mouse of my test PC, the screen turns back on, showing the screen shield, so I could understand if that counted as not stopping the screensaver, but if I press Escape and start typing a username, or click on the controls on the login screen, the shield is definitely gone, but org.gnome.ScreenSaver.GetActive still reports true, and org.gnome.ScreenSaver.GetActiveTime continues counting. That seems to me to be false reporting :)
OS: CentOS Linux 7.4 Gnome: 3.22.3
Version: 3.22.x