https://bugs.kde.org/show_bug.cgi?id=442092
Bug ID: 442092
Summary: allow infinite time before password is required to
unlock after auto-locking
Product: kscreenlocker
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: tempel.jul...@gmail.com
CC: bhus...@gmail.com
Target Milestone: ---
Currently, three minutes is the maximum value a user can set. However, this is
still annoying when kscreenlocker is mostly used as a screensaver, as chances
are you don't want to always enter your password after three minutes.
Perhaps not using a password for a user can be a workaround in some scenarios,
but there are quite some reasons why an option to turn off auto-locking would
be the better choice:
-Users shouldn't be encouraged not to use passwords.
-Users want to be able to deliberately lock the screen e.g. via hotkey, but
don't necessarily want auto-locking.
-I assume allowing (close to) infinite values for LockGrace config setting in
kscreenlockerrc should be easy to implement.
-So kscreenlocker should be able to easily act as a screensaver, without really
bending its purpose and not making things harder for developers in the future.
-screensaver situation is dire on Linux, especially on Wayland. kscreenlocker
already has all the DPMS and inactivity detection functionality implemented
that is required by a screensaver, so a separate screensaver program inside
KDE/Plasma would cause redundancy (and doesn't seem likely to happen).
-On Windows, screensaver and screen locker are basically the same thing.
Windows screensaver offers an option to lock the screen after the screensaver
is stopped by activity. Which in return means you can also have a screensaver
without automatic screen locking by not having the locking checkbox ticked.
--
You are receiving this mail because:
You are watching all bug changes.
