Bug 357399 - Screen doesn't lock after a timeout if power management is globally disabled
Summary: Screen doesn't lock after a timeout if power management is globally disabled
Status: RESOLVED NOT A BUG
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-01-01 18:30 UTC by Dave Flogeras
Modified: 2016-01-03 09:06 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Flogeras 2016-01-01 18:30:28 UTC 
This may be by design, but if I set a 1 minute timeout to lock my session automatically it works as expected.  If I uncheck the "Enable Power Management" in the system tray (by clicking the battery icon first), the timeout no longer applies.

I would expect the power management uncheced to prevent the monitor from sleeping, and/or the machine from suspending/hibernating, but do not expect the lock time to be affected.  If this is by design, just close it.

Tested on 5.4.3 machine.

Reproducible: Always
Comment 1 Kai Uwe Broulik 2016-01-01 19:04:25 UTC 
This is intentional. When watching a video you want neither your screen turn off, nor have it lock. We're currently discussing a possible solution for this problem.
Comment 2 Kai Uwe Broulik 2016-01-01 19:05:42 UTC 
May I ask why you uncheck this checkbox in the first place? Is it some application not properly blocking power management when you would expect it to (presentation, video playback, etc)?
Comment 3 Dave Flogeras 2016-01-01 19:19:20 UTC 
I only noticed when testing https://bugs.kde.org/show_bug.cgi?id=357368

I thought it may be unintentional, but when you explain it as above (for uninterrupted presentation/video watching) it makes complete sense to prevent the idle timeout.  My gut feeling was incorrect. Sorry for the noise :)
Comment 4 Martin Flöser 2016-01-03 09:06:12 UTC 
given the description -> not a bug