On Sun, 19 Aug 2018 11:49:52 +0200 =?UTF-8?Q?Arnaud_Court=c3=a8s?=
<[email protected]> wrote:
> I run Debian Testing on my computer and before geoclue-2.0 upgrade on
> 2018-08-17, Redshift worked perfectly fine with geoclue in version 2.4.7.
>
> Now, everytime Redshift is launched, I have the following error :
> "Unable to start GeoClue client:
> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift'
> disallowed, no agent for UID 1000.
> Unable to connect to GeoClue."
>
> I tried the little trick by modifying the geoclue.conf file and adding a
> specific section for Redshift but it doesn't work for me and doesn't
> change anything in the error.
>
> Maybe something more to do on geoclue-2.0 package ? Something else to
> try on my side ? Redshift is buggy ?
Same problem here. :-(
So far the workarounds seem to assume knowledge of how all of this fits
together. Right! I have it working. Here are some simple steps:
1. Install geoclue-2-demo
2. If you don't want to be asked if redshift can do geolocation, make
the configuration change mentioned in message #25
If you don't do this then there will be a pop-up each time
redshift-gtk is started asking if redshift should be allowed to do
geolocation.
3. Either logout+login to start the demo agent or run the demo agent by
hand:
/usr/lib/geoclue-2.0/demos/agent &
4. Now redshift-gtk (and, I suppose, redshift) should be able to
connect to the demo agent when started.
peace & happiness,
martin
