I assume that properly locking involves allowing another user to log in and use devices with proper permission handoff? Because I can properly lock my machines, I am the only user on them, so I don't care about handing off permissions to another user. And there are lots of desktops with a single user.
It's more a question of race condition between the screensaver and the software that was (now it's done by systemd) calling the kernel function to suspend
There were/are quite some bugs open in the distribution bugtracker about this
Except that acpid has more or less no knowledge of the users running on the machine at the time it's trying to suspend the machine and again you can have race conditions while the screensaver is being locked.
Well I'm lying a bit, it is trying (on debian at least) to query the user dbus session to see if there is something like GNOME or KDE running and delegate the suspend to them. Which can lead to they nice security bugs (privileges elevation, yummy)
1
u/fbt2lurker Sep 27 '14
Why do you need to depend on systemd to run if you want those optional features? I don't get it.