why am I not surprised that sending a cryptic dbus command is the "correct" way to lock the screen from the cli these days.
in any case, I can run that command as often as you like, and it always returns success to the shell, but it never locks the screen: tessa@boxxy:~/Downloads$ dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock tessa@boxxy:~/Downloads$ echo $? 0 tessa@boxxy:~/Downloads$ dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock tessa@boxxy:~/Downloads$ echo $? 0 looking at the journalctl output right after running, I see the following, which is clearly incorrect: Sep 23 15:07:58 boxxy gnome-shell[209336]: Screen lock is locked down, not locking so it appears as if it thinks the screen is already locked, even though I'm interacting with my session. and the dbus call doesn't have any way of returning an error state to the cli if the operation fails, which is honestly such a bad design, as it leaves things that rely on it silently failing all over the interface but claiming they're working correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1896416 Title: screen locking no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
