[Bug 1093592] New: redshift doesn't work after geoclue2 update
http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Bug ID: 1093592 Summary: redshift doesn't work after geoclue2 update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening@forge.provo.novell.com Reporter: dmarcoux@posteo.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 770512 --> http://bugzilla.opensuse.org/attachment.cgi?id=770512&action=edit redshift error Hello, I updated to the latest snapshot (2018 05 15) and since then, redshift with geoclue2 doesn't work. After launching, it displays an error (see attachment). This wasn't happening with the previous snapshot I had, but I'm not sure which one. The issue seems to arise due to changes within the recent revisions of the geoclue2 package, so as far as 2 months ago. So by looking at the snapshots, I suspect it is in one of those: - 2018 03 04 - 2018 04 24 - 2018 05 11 - 2018 05 13 The workaround is to provide the latitude and longitude manually with the option -l. -- 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#c1 Łukasz Konieczny <ftefrjbhfvasf32@o2.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ftefrjbhfvasf32@o2.pl --- Comment #1 from Łukasz Konieczny <ftefrjbhfvasf32@o2.pl> --- I have the same problem. I'm using KDE Plasma with redshift plasmoid. I have tried to run geoclue from services manager in YaST and then i had the popup window with message that there is no install section in description file of geoclue service. I have looked into /usr/lib/systemd/system/geoclue.service and indeed there is no [Install] section. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Łukasz Konieczny <ftefrjbhfvasf32@o2.pl> 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#c2 --- Comment #2 from Dany Marcoux <dmarcoux@posteo.de> --- I have found a fix for this. The file '/etc/geoclue/geoclue.conf' needs to have the following lines: [redshift] allowed=true system=false users= Source: https://wiki.archlinux.org/index.php/redshift#Automatic_location_based_on_Ge... -- 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 <madworm_de.novell@spitzenpfeil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madworm_de.novell@spitzenpf | |eil.org --- Comment #3 from robert spitzenpfeil <madworm_de.novell@spitzenpfeil.org> --- 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 http://bugzilla.opensuse.org/show_bug.cgi?id=1093592#c4 Moritz Duge <duge@pre-sense.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |duge@pre-sense.de --- Comment #4 from Moritz Duge <duge@pre-sense.de> --- Since version 15.4 openSUSE-LEAP is affected too. (was working fine until 15.3) See: bug 1200355 -- 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 <Andreas.Stieger@gmx.de> 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#c5 --- Comment #5 from Tejas Guruswamy <masterpatricko@gmail.com> --- *** Bug 1200355 has been marked as a duplicate of this bug. *** -- 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 <masterpatricko@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #6 from Tejas Guruswamy <masterpatricko@gmail.com> --- 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.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 http://bugzilla.opensuse.org/show_bug.cgi?id=1093592#c7 Tejas Guruswamy <masterpatricko@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Tejas Guruswamy <masterpatricko@gmail.com> --- So in summary Tumbleweed should be working fine, and I will close this as fixed. But I am aware Leap 15.4 is not working, and as far as I can tell it would need GeoClue update to properly fix. If there is strong motivation for that, please speak up. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com