https://bugs.kde.org/show_bug.cgi?id=476962
--- Comment #3 from Jakob Petsovits <j.acco...@petsovits.com> --- The fix was simple, removing the check for > 0s in the code (https://invent.kde.org/plasma/powerdevil/-/blob/3de931d603796c8d245f775a50f5e178e0564d93/daemon/actions/bundled/dpms.cpp#L191) will do the trick. This made the screen turn off immediately after locking. Plot twist: When I wanted to unlock the screen, I wasn't able to anymore because PowerDevil would immediately activate the dim-and-turn-off effect, which apparently also prevents input and caused lots of flickering when I just wanted to enter my password. Maybe it's not such a great idea to let people configure immediate turn-off? Should we assign a non-zero lower bound? -- You are receiving this mail because: You are watching all bug changes.
