Okay, here's an EVER WEIRDER UPDATE! The interactions between xscreensaver and systemd are determined by xscreensaver-systemd.
So I killed xscreensaver-systemd and then ran xscreensaver-systemd -verbose to look at the terminal output. AND I COULDN'T REPRODUCE THE BUG!!! Having “lock screen after X minutes” enabled led to a normal suspension of the system, and NO MORE ERROR MESSAGES after a while. ---- xscreensaver-systemd: 22:18:44: connected xscreensaver-systemd: 22:18:50: exec: xscreensaver-command -verbose -suspend xscreensaver-command: ClientMessage ignored while authentication dialog is active xscreensaver-systemd: 22:18:51: exec: "xscreensaver-command -verbose -suspend" exited with status 255 xscreensaver-systemd: 22:18:54: exec: xscreensaver-command -verbose -deactivate xscreensaver-command: ClientMessage ignored while authentication dialog is active xscreensaver-systemd: 22:18:54: exec: "xscreensaver-command -verbose -deactivate" exited with status 255 xscreensaver-systemd: 22:19:24: exec: xscreensaver-command -verbose -suspend xscreensaver-command: suspending. xscreensaver-systemd: 22:19:29: exec: xscreensaver-command -verbose -deactivate xscreensaver-command: deactivating. xscreensaver-systemd: 22:19:54: exec: xscreensaver-command -verbose -suspend xscreensaver-command: suspending. xscreensaver-systemd: 22:19:57: exec: xscreensaver-command -verbose -deactivate xscreensaver-command: deactivating. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982730 Title: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver Status in systemd package in Ubuntu: Confirmed Bug description: Test hardware - HP Elitebook 8570p, 16 GB RAM, 1 TB SSD, 3rd gen i5 CPU. Test was done within a GNOME Boxes VM, 2 GB RAM, 20 GB disk space, SeaBIOS. Steps to reproduce: 1: Install Lubuntu 22.04 into a VM. 2: Run "sudo apt update && sudo apt -y full-upgrade" to get the VM up-to-date. 3: Reboot the VM. 4: Open XScreenSaver, and check the "Lock Screen After" box. 5: Close XScreenSaver. 6: Click the Application Menu, hover over "Leave", and click "Suspend", then click "OK". Expected result: The VM should immediately go into sleep mode without any errors. Actual result: The screen goes black, then the following text appears on the screen: xscreensaver: XX:XX:XX: not launching hack (throttled.) xscreensaver: XX:XX:XX: LOCK CLientMessage received while already locked. If you move the mouse, an XScreenSaver prompt will appear asking for your username and password. If you simply leave the VM for long enough it will eventually go into suspend. If you sign in, the following error message will be present on the screen in a window: Failed to run "xdg-screensaver lock". Ensure you have a locker/screensaver compatible with xdg-screensaver installed and running. Leaving the VM alone at this point will also eventually result in it going into suspend. Clicking the "OK" button on the error window will result in the VM immediately suspending. Notes: I don't actually know what package this should be reported against - I chose lxqt-session because a look at the LXQt source code revealed that it was possible that the "Suspend" button in the LXQt Application Menu was from lxqt-session. Other packages this bug might be in include XScreenSaver, liblxqt, lxqt-powermanagement, systemd, or whatever provides DBus (is that even provided by a package? *shrug*). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-session 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Mon Jul 25 02:04:25 2022 InstallationDate: Installed on 2022-07-25 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: lxqt-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
