Description of problem: Since some days, Redshift / Redshift-gtk can not connect to "geoclue2". No function. Message: Failed to run Redshift Trying location provider "geoclue2" ... Waiting for initial location to become available... poll: interrupted system call Unable to get location from provider. Tested in Mageia 7 64-bit, LXQt Desktop.
No problem here: $ redshift Trying location provider `geoclue2'... Using provider `geoclue2'. Using method `randr'. Waiting for initial location to become available... Location: xx.67 N, xx.19 E
CC: (none) => geiger.david68210
Trying M7 beta 3, Classic 6-desktop install, Cinnamon desktop: redshift-common-1.12-3.mga7.noarch.rpm geoclue-2.5.1-2.mga7.x86_64.rpm redshift-1.12-3.mga7.x86_64.rpm $ redshift -v Trying location provider `geoclue2'... Using provider `geoclue2'. Solar elevations: day above 3.0, night below -6.0 Temperatures: 6500K at day, 4500K at night Brightness: 1.00:1.00 Gamma (Daytime): 1.000, 1.000, 1.000 Gamma (Night): 1.000, 1.000, 1.000 Using method `randr'. Waiting for initial location to become available... Location: 45.66 N, 0.98 E Colour temperature: 6500K Brightness: 1.00 Status: Enabled Period: Daytime So this looks good. I will try from LXQt also.
CC: (none) => lewyssmith
Installed & using LXQt. Trying redshift as above, exactly the same good result.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
What does 'systemctl status geoclue' say? I can see: geoclue[1699]: Failed to query location: Forbidden And https://location.services.mozilla.com/v1/geolocate?key=geoclue used by geoclue returns "You have exceeded your daily limit."
CC: (none) => jani.valimaa
(In reply to Jani Välimaa from comment #4) > And https://location.services.mozilla.com/v1/geolocate?key=geoclue used by > geoclue returns "You have exceeded your daily limit." Seems that the URL is used for the wifi geolocation service, but it's enabled by default.
In German: $ redshift -v Standortanbieter »geoclue2« wird versucht … Anbieter »geoclue2« wird verwendet. Sonnenstand: Tag oben 3.0, Nacht unten -6.0 Farbtemperatur: 6500K tagsüber, 4500K nachts Helligkeit: 1.00:1.00 Gamma (Tagsüber): 1.000, 1.000, 1.000 Gamma (Nachts): 1.000, 1.000, 1.000 Methode »randr« wird benutzt. Es wird gewartet, bis der anfängliche Standort verfügbar ist … ------ $ systemctl status geoclue ● geoclue.service - Location Lookup Service Loaded: loaded (/usr/lib/systemd/system/geoclue.service; static; vendor preset: dis> Active: active (running) since Thu 2019-04-25 21:09:28 CEST; 2min 49s ago Main PID: 3356 (geoclue) Memory: 10.1M CGroup: /system.slice/geoclue.service └─3356 /usr/libexec/geoclue Apr 25 21:09:26 localhost.localdomain systemd[1]: Starting Location Lookup Service... Apr 25 21:09:28 localhost.localdomain systemd[1]: Started Location Lookup Service. Apr 25 21:10:09 localhost.localdomain geoclue[3356]: Failed to query location: Forbidd> lines 1-11/11 (END)
Same as Comment 4 and Comment 5
Would it be an idea to get our own API key? https://location.services.mozilla.com/api
CC: (none) => smelror
(In reply to Stig-Ørjan Smelror from comment #8) > Would it be an idea to get our own API key? > > https://location.services.mozilla.com/api See also wally's mail on dev ml: https://ml.mageia.org/l/arc/dev/2019-04/msg00268.html
CC: (none) => marja11Status: UNCONFIRMED => NEWSummary: Redshift - can not connect to geoclue2 => Redshift - can not connect to geoclue2, a Mozilla Location Service API key for Mageia can solve thatEver confirmed: 0 => 1
Hm. Today it works again. And the Link in Comment 4 reports my location again, too.
Closing as works for me. Maybe reopen (like for the "Mozilla Location Service API key for Mageia can solve that")
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED
Sorry. Have to reopen. Maybe an own API Key/something which is more reliable would be good. ---- https://location.services.mozilla.com/v1/geolocate?key=geoclue error code 403 message "You have exceeded your daily limit." errors 0 domain "usageLimits" message "You have exceeded your daily limit." reason "dailyLimitExceeded"
Resolution: WORKSFORME => (none)Status: RESOLVED => REOPENED
Alright. Geoclue 2.5.2 has been pushed to Cauldron. It may fix the daily limit issue we've been seeing. https://gitlab.freedesktop.org/geoclue/geoclue/issues/113#note_157526
(In reply to Stig-Ørjan Smelror from comment #13) > > Geoclue 2.5.2 has been pushed to Cauldron. It may fix the daily limit issue > we've been seeing. > > https://gitlab.freedesktop.org/geoclue/geoclue/issues/113#note_157526 Thanks, Stig :-) Assuming that fixed this issue, as explained there. Closing @ psyca Please reopen this report if you still have this issue with geoclue-2.5.2-2.mga7 (If you have a custom configuration, then skip geoclue-2.5.2-1.mga7)
Status: REOPENED => RESOLVEDResolution: (none) => FIXED