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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1896416 Title: screen locking no longer works Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: New Bug description: in the last week, the gnome screen locking functionality stopped working. I'm under the impression this is handled by gdm3, but if not, please point me at the correct package. in any case, now there's no lock icon in the power menu in the top right, win-L does nothing, and trying to invoke manually with the gnome-screensaver package times out after about a minute with the following error: $ gnome-screensaver-command -l ** (gnome-screensaver-command:212161): WARNING **: 18:46:25.014: unable to send message: Timeout was reached ** Message: 18:46:25.014: Did not receive a reply from the screensaver. as well, if I suspend the system, on resume it dumps right back to the desktop without a prompt to re-authenticate, so this is a security issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 18:47:40 2020 InstallationDate: Installed on 2020-07-15 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
