Change:
fails like this: system: host os: multi-user?: sandbox: version: channels(sean): channels(root): nixpkgs:
This should be fixed on recent unstable.
It's still not working for me.
What DE are you using? Do you get a notification asking you to allow redshift access to the location?
I'm using awesome without a desktop environment. I would try to install one, but that seems to be broken as well: Could this be done DE-agnostically by adding lines to ?
No. The breakage is due to geoclue now requiring an agent to be running. I have an issue open to allow the whitelist to work even if there is no agent running. Go comment on if you'd like this to work.
That's because the option is called Also are you sure you did ? Where is redshift being whitelisted?
You don't need to turn on the geoclue service, the redshift module does that. Redshift isn't whitelisted because there's no point, because it doesn't work. If the issue I linked to is fixed, then we could do that.
Thanks for clarifying FTR.
The seems to have been fixed, but I guess what's left to do is whitelisting redshift in ?
Experiencing this issue on - is there a way to work around this somehow?(apart from explicitly passing the coordinates)
there is no upstream release with the relevant commit yet. And yes, we would need to update the config file, ideally with something like Then we can get rid of most of what DE are you using? You should get a notification asking you to give permission for redshift to access the location. Hopefully we'll be able to ditch this once upstream make an new release.
I'm not using a DE. I'm running via The implementation uses to run the WM. Here's the generated by : Here are the contents of in my case: I also have this in my config: So that's the resulting I end up with on my local machine: And :
Well, my understanding of the geoclue dev's position was that it should only work in a desktop environment that can prompt the user for permission to access the location. I think that's crazy, but that's where we are right now. Hopefully once they release a version with that patch then we can do something more sensible.
From the dev's : If I read this correctly, we'll still have to whitelist redshift and add , to make sure it works for non-flatpak users.
Yes, see the PR I linked.
As of 2.5.0, is built with : any idea how to use in ? I was looking for some supporting functions but couldn't find any.
Lots of the gnome packages are built with meson.
ERROR: Meson version is 0.46.1 but project requires = 0.47.2. but the upgrade is .
See
I've been away from this issue long enough to forget where the problem actually lies :) do you know what the status of this is?
It's complicated. As of the new version we can probably now just edit the config file (hard to tell, they've been changing things and there is no documentation). The best way to do that is a nixos module, i.e.
The aforementioned change has been completed (). Pretty sure if you use the example in this commit this can work as expected.

Discussion:
# needed so that .desktop files are installed, which geoclue cares about environment.systemPackages = [ cfg.package ]; <del> services.geoclue2.enable = mkIf (cfg.provider == "geoclue2") true; </del> <ins> services.geoclue2 = mkIf (cfg.provider == "geoclue2") { enable = true; appConfig."redshift" = { isAllowed = true; isSystem = true; }; }; </ins> systemd.user.services.redshift = let