Change:
conf.set_quoted('LOCALEDIR', localedir) -conf.set_quoted('SYSCONFDIR', sysconfdir) +conf.set_quoted('SYSCONFDIR', get_option('sysconfdir')) <ins> conf.set_quoted('MOZILLA_API_KEY', get_option('mozilla-api-key')) </ins> conf.set10('GCLUE_USE_3G_SOURCE', get_option('3g-source')) conf.set10('GCLUE_USE_CDMA_SOURCE', get_option('cdma-source')) <del> conf.set10('GCLUE_USE_MODEM_GPS_SOURCE', get_option('modem-gps-source')) </del> diff --git a/meson_options.txt b/meson_options.txt index 83bc60e..b726329 100644 --- a/meson_options.txt +++ b/meson_options.txt <del> @@ -34,3 +34,6 @@ option('systemd-system-unit-dir', </del> <ins> @@ -34,6 +34,9 @@ option('systemd-system-unit-dir', </ins> option('dbus-srv-user', type: 'string', value: 'root', description: 'The user (existing) as which the service will run') +option('sysconfdir_install', +       type: 'string', value: '', +       description: 'sysconfdir to use during installation') <ins> option('mozilla-api-key', type: 'string', value: 'geoclue', description: 'Your API key for Mozilla Location Service') </ins>

Discussion:
Describe the bug geoclue2 service doesn't work at the moment of writing this. It seems we're hitting the problem of too many requests with default token . (). This also prevents redshift service from starting correctly when location provider is set to geoclue2. To Reproduce Steps to reproduce the behavior: location provider to geoclue Additional context I'm not sure if API is limitting based on api key or something machine specific like IP address. Notify maintainers Metadata Please run and paste the result. Maintainer information:
Thanks for looking into this! I was wondering why occasionally redshift would get stuck waiting for the location. It looks like Mozilla is recommending that distros register their own key now that they're finding heavy load on the geoclue key:
Yeah, so the solution as mentioned is we have to register our own key.
I think we're on the same page then. I also wanted to recommend that. Do we know who can take care of it?
I was just looking at the API key request form. I would be happy to fill out this form and be in contact with people at mozilla to recieve a key. They state in the form "As Mozilla offers MLS as a free service, we cannot provide keys to everyone who requests one. Your request is more likely to be granted if you provide a detailed explanation of your project and intended use. ", so I guess I need to flex NixOS as deserving and relevant in order to receive a key I guess :grin:
great thanks for taking care of that.
Just completed it Their insistence on "being detailed" in the that form is probably going to fall away given that every distro is probably going to want one, and there's a lot of them...
Just updating that in a 1 week + time there hasn't been a response to me personally.
For the record I've hit this issues few times in meantime but almost always when I did some reboot, login or restart of the services in the evening of central European time). If that happened I just restarted the service the next day in morning. I think folks living in Americas might be likely more impacted by this (assuming they're more likely to boot at a time when this is down) but I of course don't have any data about that.

It doesn't seem to be that serious issue but certainly I still hope we will be able to get the key from Mozilla and solve it anyway.
I got a response from them. What we need to do is... :grin: Do the same thing as arch has done with patching , which will make the API key configurable. We'd then have to change the module, maybe add options and change the default and example values. And also we need to add a comment to the geoclue expression that changes to the configuration need to be monitored and the nixos module should be updated (same as NetworkManager).