redshift
redshift copied to clipboard
wrong path for .conf in README
Describe the bug
readme lists the path to place the redshift.conf file as ~/.config/redshift/redshift.conf
in case XDG_CONFIG_HOME
is not defined. The path should actually be ~/.config/redshift.conf
.
- [x] I have checked the FAQ and my issue is not mention there.
To Reproduce
- Go to
~/.config/redshift/
and place the redshift.conf. It won't get applied.
Expected behavior The configuration should get applied as written in readme
Error output/logs/screenshots
Software versions (please complete the following information):
- OS: [Linux]
- Redshift version: [1.12]
- Distribution: [Debian Bullseye]
- Redshift installed from: [using apt-get]
The reason that ~/.config/redshift/redshift.conf
is not being applied is most likely caused by: https://github.com/jonls/redshift/issues/672 (since you are on Debian).
Redshift will then fall back to the legacy path ~/.config/redshif.conf
for backward compatibility. Therefore it seems like ~/.config/redshif.conf
should be put in the README, whilst actually ~/.config/redshift/redshift.conf
is indeed the correct path.
Hope that helps.
For me it fails on both config locations
$ redshift -c ~/.config/redshift/redshift.conf
fopen: Permission denied
Unable to load config file.
as well as
redshift -c ~/.config/redshift.conf
fopen: Permission denied
Unable to load config file.
For me it fails on both config locations
$ redshift -c ~/.config/redshift/redshift.conf fopen: Permission denied Unable to load config file.
as well as
redshift -c ~/.config/redshift.conf fopen: Permission denied Unable to load config file.
Same for me
Linux 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux
Maybe https://github.com/jonls/redshift/issues/850#issuecomment-1193378198 helps. You can check whether it is indeed AppArmor that prevents redshift reading the configuration files.
I just encountered this problem on Ubuntu 23.10 after following the README. I figured out to move the conf to ~/.config
by reading man redshift
.
I think that A) the manpages and README should have consistent instructions, and B) regardless of which is the "right" path, this gotcha should be documented in both since it is clearly affecting many users.