Bug 360190 - Time to ask for password after locking doesn't work
Summary: Time to ask for password after locking doesn't work
Status: RESOLVED DUPLICATE of bug 361008
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-07 07:51 UTC by Antonio Rojas
Modified: 2016-04-04 06:10 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio Rojas 2016-03-07 07:51:43 UTC 
In 5.6 beta, the option to set a time to ask for the password after locking the screen doesn't work: the password is required immediately after the screen is locked regarded of the value set in the KCM.

Reproducible: Always
Comment 1 Martin Flöser 2016-03-07 10:22:14 UTC 
which Qt version are you using?
Comment 2 Antonio Rojas 2016-03-07 10:25:48 UTC 
(In reply to Martin Gräßlin from comment #1)
> which Qt version are you using?

5.6-rc
Comment 3 Martin Flöser 2016-03-07 12:55:41 UTC 
yep, thought so. I experienced the same problem once I upgraded Qt to 5.6 last week. KScreenlocker wasn't changed, though. So I think it's more Qt 5.6 related than Plasma 5.6 related.

Anyway: I hope that https://phabricator.kde.org/D957 will fix it. If you have a chance to test the patch, this would be appreciated.
Comment 4 Antonio Rojas 2016-03-07 19:53:06 UTC 
Works fine with the patch, yes
Comment 5 Antonio Rojas 2016-03-09 09:53:58 UTC 
Well, in fact, with the patch there is the opposite problem now: the password is never required.
Comment 6 Gordon 2016-04-04 05:55:20 UTC 
I can confirm this bug in KDE Plasma 5.6.1 with Qt 5.6.0 on OpenSUSE Leap 42.1 where the time delay specified for "Require password after locking" is ignored and a password is required immediately after locking.
Comment 7 Martin Flöser 2016-04-04 06:10:01 UTC 

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