http://bugzilla.opensuse.org/show_bug.cgi?id=1200355 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger@gmx.de, | |masterpatricko@gmail.com, | |matthias@mailaender.name Assignee|screening-team-bugs@suse.de |masterpatricko@gmail.com Summary|Access to the current |redshift: access to the |location was denied by |current location was denied |GeoClue! (openSUSE-15.4, |by GeoClue |REGRESSION) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1200355 http://bugzilla.opensuse.org/show_bug.cgi?id=1200355#c3 --- Comment #3 from Moritz Duge --- (In reply to Tejas Guruswamy from comment #2)

If this is really just an issue with the GeoClue permissions there's nothing redshift can directly do about it. Either users need to add permissions manually (there is no scope for a drop-in file from redshift) or GeoClue maintainers need to add redshift as default-allowed.

If there would be a /etc/geoclue/geoclue.conf.d/ Redshift could add it's own permission config. But because there is only a /etc/geoclue/geoclue.conf I guess the GeoClue maintainers must have a look at this ticket.

But I am curious, because I don't see right now where the GeoClue permissions have changed between 15.3 and 15.4. So how was it working before?

I can't answer that. I can only say, that it works on an openSUSE 15.3 system, but doesn't work with 15.4. You can simply test it using a 15.3 and a 15.4 live cd. https://download.opensuse.org/distribution/leap/15.3/live/ https://download.opensuse.org/distribution/leap/15.4/live/ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1200355 http://bugzilla.opensuse.org/show_bug.cgi?id=1200355#c5 --- Comment #5 from Moritz Duge --- (In reply to Tejas Guruswamy from comment #4)

[...] In the meantime could you please confirm that on your system that manual permissions added to geoclue.conf fixes the problem?

[redshift] allowed=true system=false users=

Actually further investigations showed a quite strange behavior. That setting for the geoclue.conf seems not to help at all. But the geoclue sometimes just works if I start it again after the crash. I guess it's more efficient if you take your time and reproduce it yourself. It's pretty easy to reproduce it using the live cd. The bug appears on every openSUSE-15.4 system I tried. And I'm neither a RedShift nor a GeoClue developer. So I don't have any special insights. If you unexpectedly can't reproduce it I'll gladly help! Using the KDE live cd right after booting. Same with and without modified geoclue.conf. Also waiting some time after boot before starting RedShift change the behavior. In any case the first RedShift start always fails. And sometimes the second RedShift start also fails, but then the third works fine. ######################################## linux@localhost:~> uptime 11:23:45 up 0:02, 3 users, load average: 0.91, 0.44, 0.17 linux@localhost:~> redshift Trying location provider `geoclue2'... Using provider `geoclue2'. Using method `randr'. Waiting for initial location to become available... Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' disallowed, no agent for UID 1000. Access to the current location was denied by GeoClue! Make sure that location services are enabled and that Redshift is permitted to use location services. See https://github.com/jonls/redshift#faq for more information. Unable to get location from provider. linux@localhost:~> redshift Trying location provider `geoclue2'... Using provider `geoclue2'. Using method `randr'. Waiting for initial location to become available... Location: 53.56 N, 9.96 E ######################################## -- You are receiving this mail because: You are on the CC list for the bug.