From ArchWiki

Day and night transition

I undid the last changes on the config file about the day/night transition. Sorry, but it doesn't seem to be correct. When I initially created the page, I copied the config file from upstream (including the comments). It seems to be working fine for me. Does anyone else think it is wrong? -- 6arms1leg (talk) 09:59, 29 October 2015 (UTC)Reply[reply]

Strange, I'm using redshift-1.10 and the following configuration


; Moscow
doesn't disable transition period between day and night for me (neither is -r option; that it is equivalent with transition=0 can be seen from the source code of redshift).
Transition between day and night is controlled by elevation-high and elevation-low configuration values. I just checked that if they are set to the same value (e.g. 0.0), then day-night change will be instant, even if transition=1. And if they are left different, gradual day-night transition will occur, even if transition=0.
I am using Gentoo, not Archlinux, but I don't think there is a difference between distributions. Gentoo does not have any patches for redshift-1.10, neither appears to have Archlinux. -- July.tikh (talk) 17:45, 27 October 2015 (UTC) (Copied response over from my wiki talk page. -- 6arms1leg (talk) 10:05, 29 October 2015 (UTC))Reply[reply]
When you say “It seems to be working fine for me.”, what do you mean exactly? transition=1 is the default, so this part of upstream config will always “work fine”. Did you test transition=0, did it disable day/night transition? My point is that it won't. July.tikh (talk) 10:22, 29 October 2015 (UTC)Reply[reply]
Yes, you are right, it does not work as described in the comments of the config file. I still think though that the comments in the config file in this wiki are the wrong place for that information. I added a note with your findings right before the config file. I hope you are OK with that. Feel free to improve the information. Far more important, there should be filed a bug report on the Redshift project page. -- 6arms1leg (talk) 12:47, 31 October 2015 (UTC)Reply[reply]
I raised it as an issue on the Redshift project page. -- 6arms1leg (talk) 13:20, 31 October 2015 (UTC)Reply[reply]
I don't think it is a bug, I find behavior of the program itself rather consistent. I still think documentation is just vague on what transition is handled by what option; and comments in example configuration are wrong. I commented in your bug report accordingly.July.tikh (talk) 18:05, 31 October 2015 (UTC)Reply[reply]

systemd service

The provided systemd service file (redshift.service) does not run out of the box.
The troubleshooting section mentions that, depending on your environment, you may need to delete the "After" line from the server. That alone, is not sufficient, as the service still does not know the active display - so you still need something like "Environment=DISPLAY=:0".

I'm not exactly sure where to put this in the article, so I'll just leave this here for now.
Xandaros (talk) 06:29, 19 September 2018 (UTC)Reply[reply]

If the service is not working it should be either fixed or removed. -- Ubone (talk) 09:48, 19 September 2018 (UTC)Reply[reply]

GeoClue service restarting continuously

After installing geoclue2 and configuring access from Redshift, journalctl --follow --unit geoclue.service shows the service restarting pretty much exactly every six seconds. It can't be stopped or disabled, and running it manually produces this output:

$ /usr/lib/geoclue
(geoclue:726): Geoclue-CRITICAL **: 14:30:51.437: Failed to acquire name 'org.freedesktop.GeoClue2' on system bus or lost it.

I can't uninstall it yet, so I'm stuck with running redshift -l LAT:LONG and a continuously restarting broken service.

L0b0 (talk) 01:34, 13 October 2018 (UTC)Reply[reply]