Bug 266194 - please add "disable screensaver" option to powermanagement profiles
Summary: please add "disable screensaver" option to powermanagement profiles
Status: RESOLVED WORKSFORME
Alias: None
Product: solid
Classification: Unmaintained
Component: powermanagement (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR minor
Target Milestone: 4.11
Assignee: Dario Freddi
URL:
Keywords:
Depends on: 318461
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-13 12:34 UTC by Daniel Mader
Modified: 2015-02-16 12:31 UTC (History)
4 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 Daniel Mader 2011-02-13 12:34:46 UTC
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

Currently, there is no way of simply turning off the screensaver for certain powermanagement profiles. Since more and more stuff happens within the browser, nothing stops the screensaver from kicking in, even in the Presentation profile (which apparently got lost, btw).

Would be nice to have a simple solution for all the many apps that don't talk to the screensaver...

Reproducible: Always
Comment 1 Alex Fiestas 2013-03-03 15:53:56 UTC
We should definitively implement this.
Comment 2 Oliver Henshaw 2013-03-04 16:29:51 UTC
Firstly, browsers should be inhibiting the screensaver/screen power saving - see https://bugzilla.mozilla.org/show_bug.cgi?id=811261 and http://code.google.com/p/chromium/issues/detail?id=103932

Disabling power management in the battery applet will also inhibit the screenlocker but selecting "Never shutdown the screen" for an activity will not. This is fixable by having the screenlocker ask powerdevil whether it should lock or by having powerdevil inhibit the screenlocker which will in turn inhibit powerdevil.

Mildly tangled interactions like these are why I suspect all policy should be in one process.
Comment 3 Kai Uwe Broulik 2015-02-16 12:31:49 UTC
Screen saver is now being blocked by a PM inhibition, and most browsers handle that nowadays when eg. watching a movie.