Comment 9 for bug 1982730

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.