https://bugs.kde.org/show_bug.cgi?id=439814
onit...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |onit...@gmail.com
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from onit...@gmail.com ---
I can confirm this.
It started happening some time ago, but I don't remember when exactly. And it
may not even be a Plasma issue, but a change in systemd behavior.
I suspect it's either because kscreenlocker takes too long to activate, or
because it doesn't block suspension until the lock screen is up.
Is that even possible? This StackExchange answer suggests it is a wider issue
with the way systemd handles suspend:
https://unix.stackexchange.com/questions/643511/cinnamon-screen-stays-unlocked-1-second-after-opening-lid-suspend-resume
Blocking systemd for a fixed number of seconds could help, but it's not a
robust solution. Blocking indefinitely also seems like a bad idea, because it
could prevent suspend completely when a locker gets stuck.
I suppose the best fix at this point would be to always activate the locker
manually before triggering a suspend.
--
You are receiving this mail because:
You are watching all bug changes.
