http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Łukasz Konieczny changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 http://bugzilla.opensuse.org/show_bug.cgi?id=1093592#c3 robert spitzenpfeil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madworm_de.novell@spitzenpf | |eil.org --- Comment #3 from robert spitzenpfeil --- Currently it's not working for me. The location service URL given in the config files throws an error when pointed at with a web browser. This may go away spontaneously, but still... https://location.services.mozilla.com/v1/geolocate?key=geoclue --- {"error":{"code":403,"message":"You have exceeded your daily limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your daily limit.","reason":"dailyLimitExceeded"}]}} --- https://gitlab.freedesktop.org/geoclue/geoclue/issues/113 You can put in other keys, right now "test" seems to work, but that's not a permanent solution. For the time being I'll just provide coordinates to redshift manually. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P4 - Low |P5 - None CC| |Andreas.Stieger@gmx.de, | |matthias@mailaender.name Assignee|tzotsos@gmail.com |masterpatricko@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 http://bugzilla.opensuse.org/show_bug.cgi?id=1093592#c6 Tejas Guruswamy changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #6 from Tejas Guruswamy --- After a long investigation I finally understand the situation -- see https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/143 and https://github.com/jonls/redshift/issues/636 for background. Essentially redshift queries geoclue for a location, which fires up a system DBUS service. This then checks with a user authentication agent if you are allowed to get the location. The system service exists again after 60 seconds of inactivity. Failure point #1 is if no user agent is running. In the current geoclue package the user authentication agent is started by desktop autostart (/etc/xdg/autostart/geoclue-demo-agent.desktop) so if you are not running a desktop login, you cannot use GeoClue. This failure is consistent and can be avoided by manually starting the demo agent first. In GeoClue prior to 2.5.7, you could work around the need for an agent by adding a stanza to the geoclue.conf file. But with GeoClue 2.5.7 (in Leap 15.4) the agent checks became more strict and that no longer applies. This is intentional by the GeoClue devs. Failure point #2 is that the GeoClue system service was not waiting long enough for the authentication agent to respond. (Hence why running the query twice sometimes works). This failure is essentially a GeoClue bug and can be fixed by upgrading to GeoClue 2.6.0 (already in Tumbleweed). If those still using redshift on Leap 15.4 can detail exactly what their expectations and use cases are for redshift+geoclue, I can see if any other workarounds are possible; but the core problems are not with redshift. Note that both GNOME and KDE Plasma now have built-in equivalents to redshift so it's unlikely to receive any further upstream maintenance. -- You are receiving this mail because: You are on the CC list for the bug.