Public bug reported: Affected version ubuntu1804.4/20.04
Bug summary Click Lock menu (especially click lock button very soon after login), the screen is locked as expected. But in this case, there is no org.gnome.ScreenSaver related dbus generated, and less way to report screen is locked. Using dbus-monitor also couldn't be able to recevie the screenSaver dbus message. Steps to reproduce Put attached test.sh under /tmp/test.sh Put attached screen-status-monitor.desktop to /etc/xdg/autostart/screen-status-monitor.desktop Click Lock menu very quickly after login Verify /tmp/result, the first "true/false" is to query dbus org.gnome.screensaver.GetAcitve, the second is to query session lock status from loginctl utility, they both indicate "unlocked" status. What happened the query result is "unlocked" status What did you expect to happen the query result is "locked" status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: dbus gnome-shell ** Attachment added: "script.zip" https://bugs.launchpad.net/bugs/1901109/+attachment/5425739/+files/script.zip -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1901109 Title: Failed to detect screen is locked sometimes by dbus or loginctl utility when click Lock menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs