Bug 361328 - Kscreenlock locks screen instantly and ignores 'require password after' timeout
Summary: Kscreenlock locks screen instantly and ignores 'require password after' timeout
Status: RESOLVED DUPLICATE of bug 361008
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-02 16:50 UTC by nothanks3u
Modified: 2016-04-04 06:09 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nothanks3u 2016-04-02 16:50:15 UTC
Settings: [YES] Lock screen automatically after 5 minutes
Require password after locking: 5 sec
Lock screen on resume [YES]

Previously in Kscreenlock 5.5, the locked screen banner would appear and if you moved your mouse within 5 second, it would close and return you to your desktop without needing your password (expected behavior)

Now in Kscreenlock 5.6, settings have not changed but as soon as the screen lock banner appears, the PC is locked, the 5 second timeout selected is entirely ignored and you need a password to unlock it all the time now (this is wrong behavior)

Reproducible: Always

Steps to Reproduce:
1. Follow setup in details
2. Leave screen for 5 minues
3. Move mouse when banner appears

Actual Results:  
Password is required for unlocking

Expected Results:  
Login request window should close automatically without password

Using Arch linux (not testing branches)
Comment 1 Rog131 2016-04-02 18:05:57 UTC
Duplicate of the https://bugs.kde.org/show_bug.cgi?id=361008 ?
Comment 2 nothanks3u 2016-04-02 19:21:27 UTC
Yes appears to be a duplicate. You've got another bug then because when I submitted the bug (I've just checked again) it's showing the top 100 kscreenlocker bugs are 'no bugs were found'.
Comment 3 Martin Flöser 2016-04-04 06:09:52 UTC

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