For those who wants bluelight control without geoclue, just create redshift.conf in .config directory and replace xxx and zzz by your latitude and longitude. Code: ; Global settings for redshift [redshift] ; Set the day and night screen temperatures temp-day=5700 temp-night=3500 ; Disable the smooth fade between temperatures when Redshift starts and stops. ; 0 will cause an immediate change between screen temperatures. ; 1 will gradually apply the new screen temperature over a couple of seconds. fade=1 ; Solar elevation thresholds. ; By default, Redshift will use the current elevation of the sun to determine ; whether it is daytime, night or in transition (dawn/dusk). When the sun is ; above the degrees specified with elevation-high it is considered daytime and ; below elevation-low it is considered night. ;elevation-high=3 ;elevation-low=-6 ; Custom dawn/dusk intervals. ; Instead of using the solar elevation, the time intervals of dawn and dusk ; can be specified manually. The times must be specified as HH:MM in 24-hour ; format. ;dawn-time=6:00-7:45 ;dusk-time=18:35-20:15 ; Set the screen brightness. Default is 1.0. ;brightness=0.9 ; It is also possible to use different settings for day and night ; since version 1.8. ;brightness-day=0.7 ;brightness-night=0.4 ; Set the screen gamma (for all colors, or each color channel ; individually) gamma=0.8 ;gamma=0.8:0.7:0.8 ; This can also be set individually for day and night since ; version 1.10. ;gamma-day=0.8:0.7:0.8 ;gamma-night=0.6 ; Set the location-provider: 'geoclue2', 'manual' ; type 'redshift -l list' to see possible values. ; The location provider settings are in a different section. location-provider=manual ; Set the adjustment-method: 'randr', 'vidmode' ; type 'redshift -m list' to see all possible values. ; 'randr' is the preferred method, 'vidmode' is an older API. ; but works in some cases when 'randr' does not. ; The adjustment method settings are in a different section. adjustment-method=randr ; Configuration of the location-provider: ; type 'redshift -l PROVIDER:help' to see the settings. ; ex: 'redshift -l manual:help' ; Keep in mind that longitudes west of Greenwich (e.g. the Americas) ; are negative numbers. [manual] lat=xxx lon=yyy ; Configuration of the adjustment-method ; type 'redshift -m METHOD:help' to see the settings. ; ex: 'redshift -m randr:help' ; In this example, randr is configured to adjust only screen 0. ; Note that the numbering starts from 0, so this is actually the first screen. ; If this option is not specified, Redshift will try to adjust _all_ screens. [randr] screen=0 windsman.
Interesting thread !! As a Linux user I chose F.lux over Redshift, and it has a dialogue box which takes those settings. Trouble is - all these apps revolve around location & time of day for NIGHT SLEEPERS !! As I live within a 3rd shift type of schedule these days, my screen brightens back up a little while before it is time for me to sleep & I've only the most basic idea what I may do to work around this - like maybe setting it for a timezone location that is 4 hours behind this one ?? Fortunately I also have some blue blocker glasses for the times that I am using the PC later than usual.
@smallhagrid, Major difference is that Redshift is FOSS and scriptable, and F.lux is closed source (download binary), i 'll tend to say that F.lux is more suitable for Windows or Mac, but of course you can use it on Linux. Imho, i always choose to install Open Source software on all my distros. windsman.
Since the topic here has been expanded to opinions about open vs. closed - here's my POV: I am a very happy Linux user & support provider while not being an OSS evangelist at all. What I care MOST about is that the stuff WORKS well. Aside of that, if it is OSS, very nice - but that is not any specific priority for me. The ONLY s/w I am against using is the sort that comes from evil monopolistic sources; I am delighted not to be working endlessly on that stuff anymore.