Sorry, I thought xscreensaver-systemd would have been started by
systemd, because it was in the name, but I'm certain now it's started by
lxqt-session, as correctly determined by the original reporter.
** Package changed: systemd (Ubuntu) => lxqt-session (Ubuntu)
--
You received this bug notific
So I just restarted my system, and I got the bug.
BUT, when I killed and reran xscreensaver-systemd, THE BUG DISAPPEARED.
This seems to indicate that xscreensaver-systemd is being run too early
in the login/startup process.
--
You received this bug notification because you are a member of Ubunt
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 afte
So here's the problem: if you have “lock screen after X minutes” enabled
in xscreensaver, and you run `systemctl suspend`, then for some reason
systemd first LOCKS the screen, which stops the suspend; only after
unlocking the screen does the system suspend.
If you uncheck “lock screen after X minu
4 matches
Mail list logo