Bug 311626 - "Require password after" is misleading
Summary: "Require password after" is misleading
Status: RESOLVED DUPLICATE of bug 310871
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_screensaver (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
Depends on:
Reported: 2012-12-13 10:16 UTC by Anne-Marie Mahfouf
Modified: 2013-04-18 15:42 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Proposed UI fix (23.55 KB, image/png)
2012-12-13 10:28 UTC, Anne-Marie Mahfouf
As it is now (22.39 KB, image/png)
2012-12-13 10:40 UTC, Anne-Marie Mahfouf

Note You need to log in before you can comment on or make changes to this bug.
Description Anne-Marie Mahfouf 2012-12-13 10:16:43 UTC
People think that when you do not check  "Require password after" then it means a password is not required and that they can unlock the screen only with the mouse

Reproducible: Always

Steps to Reproduce:
1. In kcm_screensaver, check "Start automatically after" <time>
2. Leave "Require password after" unchecked

Actual Results:  
The screen is locked and requires a password

Expected Results:  
The screen is locked but does not require a password, the mouse only will unlock it

The GUI is misleading. There should not be a checkbox  for "Require a password" and the field should not be grey.
Comment 1 Anne-Marie Mahfouf 2012-12-13 10:27:26 UTC
How it is intended to work: "Start automatically after <time>" will start the screen locker after <time>.
If "Require password after" is unchecked, the password will be required immediately.
If "Require password after" is checked, the password will be required after <time> seconds.

Proposed GUI fix attached. If "Require password after" is unchecked, the spinbox value which is grey should be set to 0 and not the previous value.
Comment 2 Anne-Marie Mahfouf 2012-12-13 10:28:34 UTC
Created attachment 75810 [details]
Proposed UI fix
Comment 3 Anne-Marie Mahfouf 2012-12-13 10:40:31 UTC
Created attachment 75811 [details]
As it is now
Comment 4 Oswald Buddenhagen 2012-12-13 10:42:18 UTC
no, this *not* what it is supposed to mean. this is simply broken functionality, because the kwin maintainers are on a crusade against classical screen savers.
Comment 5 Anne-Marie Mahfouf 2012-12-13 10:45:07 UTC
Oswald can you elaborate on how it is supposed to work then?
Comment 6 Oswald Buddenhagen 2012-12-13 11:16:56 UTC
just like it has been for the last one and a half decades: when the checkbox is not checked, no password is required. it's supposed to be a screensaver, not a screenlocker in this mode.
Comment 7 Aurelien Gateau 2012-12-13 15:17:06 UTC
There has been a proposal to improve the KCM two months ago, but unfortunately nothing came out of it: https://git.reviewboard.kde.org/r/106768/ .

Regarding this delay before password is necessary, Aaron was suggesting to simply pick a reasonable value and remove the option all together. I think it is a good idea: I don't see the benefit in being able to fine tune the delay down to the second.
Comment 8 Andrea Bocci 2013-01-10 10:06:16 UTC
Please do not remove the "Require password after XXX seconds" option.
A value that may be reasonable for somebody (e.h. 60 seconds) may be too long for somebody else (I use 10 seconds at most) - and viceversa.

Options are good :-)
Comment 9 Marcelo Sales 2013-02-07 18:41:08 UTC
This is probably related to bug #310871
Comment 10 Oliver Henshaw 2013-04-18 15:42:03 UTC

*** This bug has been marked as a duplicate of bug 310871 ***