Bug 16680 - Plasma 5 screen automatic locking does not work
Summary: Plasma 5 screen automatic locking does not work
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
Depends on:
Blocks: 17523
  Show dependency treegraph
Reported: 2015-09-01 08:57 CEST by Jüri Ivask
Modified: 2016-03-09 20:31 CET (History)
1 user (show)

See Also:
Source RPM:
Status comment:


Description Jüri Ivask 2015-09-01 08:57:00 CEST
Description of problem: screen automatic locking does not work

Version-Release number of selected component (if applicable): Plasma 5.4

How reproducible:every time

Steps to Reproduce:
1.Open Plasma 5 Systemsettings
2.Desktop Behaviour -> Screen Locking
3.Check that "Lock screen automatically" is selected and set the time eg 1 min
5.Wait the selected time and more - nothing happens

Manual screen locking works.


Steps to Reproduce:
Comment 1 Jin-tong Hu 2015-09-05 05:26:59 CEST
The same here. This function has been broken for a few weeks if I remember correctly.

CC: (none) => piscestong

Comment 2 Jüri Ivask 2015-10-14 10:26:28 CEST
Still broken in fresh Mageia 5.4.2 Plasma.
It should be Mageia specific as for example in KaOS & 5.4.1 it works OK.
Comment 3 Jüri Ivask 2015-11-23 15:55:10 CET
Still broken in fresh Mageia 5.5 beta...
Comment 4 Jüri Ivask 2015-12-18 11:00:00 CET
Still valid in fresh Plasma 5.5.1
Comment 5 Jüri Ivask 2016-01-18 11:39:37 CET
Still valid in fresh Plasma 5.5.3
Rémi Verschelde 2016-01-19 09:36:17 CET

Blocks: (none) => 17523

Comment 6 Jüri Ivask 2016-03-09 12:46:16 CET
Still valid for Plasma 5.6beta,

However it just seems, that there is a missing dependency.

Installing package kidletime makes screen automatic locking to work OK.

So it seems, that kidletime should be a dependency for kscreenlocker...
Comment 7 Nicolas Lécureuil 2016-03-09 15:07:04 CET
Just fixed on svn.
Comment 8 Jüri Ivask 2016-03-09 20:31:27 CET
Seems to be fixed.
Thanks Nicolas!

Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.