exactly why I found this report.
During debugging I noticed that redshift has the -c flag where
a user can specify a config file instead of the default and
it seems to me as if apparmor also prevents calling redshift
with `redshift -c $HOME/dotfiles/redshift.conf`.
https://manpages.debian.org/testing/redshift/redshift.1.en.html#OPTIONS
On Mon, 4 Jan 2021 20:00:29 +0100 Quentin Hibon <[email protected]> wrote:
The path $HOME/.config/redshift.conf currently does not work if it is a
symlink. That breaks the config of people keeping a dotfiles repository
and linking their configuration files from there.
On Wed, 23 Dec 2020 21:11:14 +0000 "Jeremy L. Gaddis" <[email protected]>
wrote:
> On Sun, 20 Dec 2020 22:17:19 +0100 gregor herrmann <[email protected]> wrote:
> > /etc/apparmor.d/usr.bin.redshift already has
> > owner @{HOME}/.config/redshift.conf r,
> > so reading the config file works. - Oh ~/.config/redshift/redshift.conf
> > vs. ~/.config/redshift.conf; I'm using the latter, don't know if the
> > former is supported (the manpage says
> > A configuration file with the name redshift.conf can optionally be placed
in ~/.config/
> > ).
>
> Just FYI ...
>
> Based on the README.md [0] and commit 9ff0501e [1] in the upstream
> repository, it's clear that "$XDG_CONFIG_HOME/redshift/redshift.conf"
> (i.e., "${HOME}/.config/redshift/redshift.conf") is the "preferred"
> location for the configuration file, although the "formerly used path"
> (~/.config/redshift.conf) will be used as a "fallback".
>
> The AppArmor profile should, of course, reflect that.
>
> It might be a good idea to refresh/update the README.gz file included
> in the redshift package as well.
>
> With apologies for any text formatting issues as a result of using
> Gmail as an MUA,
> -Jeremy
>
> [0]: https://github.com/jonls/redshift/blob/master/README.md
>
> [1]: https://github.com/jonls/redshift/commit/9ff0501e785e4e3fe2e8915eb9468d12cab98cf6
>
>
