https://bugs.kde.org/show_bug.cgi?id=476962
--- Comment #7 from Jakob Petsovits <j.acco...@petsovits.com> --- (In reply to Natalie Clarius from comment #6) > Why do you think we need two different settings? Imo setting it to 0s should > turn it off immediately when going unlocked -> locked but also turn on again > immediately once there is input in already locked state. Let's say that 0s is the configured timeout for sleeping when the system transitions from unlocked to locked. So it goes to sleep immediately after locking. We have also established that we can't (shouldn't) use 0s as a timeout after user input when already locked. I think it's also clear that if the user stops typing / doesn't manage to log in, there should still be a timeout (>0s) for putting the system back to sleep. We can call this a "setting" or anything else, and it doesn't have to be user-configurable, but it seems clear that another timeout value is needed apart from the original (0s) configured one. -- You are receiving this mail because: You are watching all bug changes.
