On Wed, Aug 21, 2019 at 12:36:48PM +0100, Mark Hindley wrote: > On Tue, Aug 20, 2019 at 11:19:30PM +0200, Thorsten Glaser wrote: > > >I think you might need > > > > > >HandleLidSwitch=lock > > > > > >in /etc/elogind/logind.conf for that behaviour. > > > > I’ve made a few adjustments following that suggestion (see > > below), dist-upgraded sid to ensure I’ve got the latest > > version of everything, rebooted (there was a new kernel to > > update to anyway), and… still no lock for both console and > > X11 sessions. > > > > Running xlock -mode blank manually works, so this is a > > regression from when I only had the ACPI stuff installed. > > I don't have any suitable hardware to test this directly, but > > loginctl lock-session > > doesn't work for me either.
I have found a work around. I am unsure if it is the upstream's intended route. You need xss-lock to join logind to xscreensaver: xss-lock -- xscreensaver-command -lock & loginctl lock-session Does that work for lid events too? Mark
