Bug 179093 - Backlight settings based on local time
Summary: Backlight settings based on local time
Status: RESOLVED DUPLICATE of bug 347712
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-kcm (show other bugs)
Version: unspecified
Platform: Debian testing Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-30 00:16 UTC by Roman Šmakal
Modified: 2015-05-14 12:32 UTC (History)
2 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 Roman Šmakal 2008-12-30 00:16:11 UTC 
Version:            (using KDE 4.1.3)
Installed from:    Debian testing/unstable Packages

Hello there,
it will be fine to get some advanced setting of backlight in powerdevil. My idea is to set time, when backlight will be set to lower level, because high backlight level causes eye hurts after some time in dark. But that you realize after eyes started to hurt, so manual backlight settings isnt enough.
I think it is good for your health and powersaving as well.
So what are you thinking about it?
Comment 1 Jaroslav Petráš 2008-12-30 03:04:35 UTC 
It will be nice to have a feature like this.

Summary - Wish:

- ability to set backlight intensity for day/time period
- ability to set different day/time period in year seasons (spring, summer, autumn, winter) [my wish]
Comment 2 Dario Freddi 2008-12-30 12:54:40 UTC 
Nice idea :) accepting it for 4.3
Comment 3 Roman Šmakal 2009-09-27 08:32:42 UTC 
What is progress of this bug? Looks like KDE 4.3 does not have this feature at all.
Comment 4 Jonathan Riddell 2015-03-11 19:16:53 UTC 
This bug is reported on libsolid which is the kdelibs4 version of the solid library.  It is now in maintenance mode.  If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid or Powerdevil.
Comment 5 Martin Klapetek 2015-05-14 12:32:12 UTC 

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