https://bugs.kde.org/show_bug.cgi?id=476962
--- Comment #5 from Jakob Petsovits <j.acco...@petsovits.com> --- So... two different settings? Or keep one setting, but we apply a hardcoded lower bound (say, 10s) for the "already locked, woken up on user input" case? I guess we probably only want to expose one timeout value, to avoid bombarding the user with mostly unnecessary information. (Exposing both regular and "when locked" timeouts is arguably on the more overkill side of things already.) -- You are receiving this mail because: You are watching all bug changes.
