Comment # 5
on bug 1200355
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
########################################