

Having “lock screen after X minutes” enabled led to a normal suspension of the system, and NO MORE ERROR MESSAGES after a while.

So I killed xscreensaver- systemd and then ran xscreensaver- systemd -verbose to look at the terminal output.

The interactions between xscreensaver and systemd are determined by xscreensaver- systemd.
Xscreensaver suspend lock upgrade#
UpgradeStatus: No upgrade log present (probably fresh install) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InstallationDate: Installed on (0 days ago) Other packages this bug might be in include XScreenSaver, liblxqt, lxqt-powermanag ement, systemd, or whatever provides DBus (is that even provided by a package? *shrug*). 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. Clicking the "OK" button on the error window will result in the VM immediately suspending. Leaving the VM alone at this point will also eventually result in it going into suspend. Ensure you have a locker/screensaver compatible with xdg-screensaver installed and running. If you sign in, the following error message will be present on the screen in a window:įailed to run "xdg-screensaver lock". If you simply leave the VM for long enough it will eventually go into suspend. If you move the mouse, an XScreenSaver prompt will appear asking for your username and password. Xscreensaver: XX:XX:XX: LOCK CLientMessage received while already locked. Xscreensaver: XX:XX:XX: not launching hack (throttled.) The screen goes black, then the following text appears on the screen: The VM should immediately go into sleep mode without any errors.
Xscreensaver suspend lock update#
Test was done within a GNOME Boxes VM, 2 GB RAM, 20 GB disk space, SeaBIOS.Ģ: Run "sudo apt update & sudo apt -y full-upgrade" to get the VM up-to-date.Ĥ: Open XScreenSaver, and check the "Lock Screen After" box.Ħ: Click the Application Menu, hover over "Leave", and click "Suspend", then click "OK". Test hardware - HP Elitebook 8570p, 16 GB RAM, 1 TB SSD, 3rd gen i5 CPU.
