Hello, Le 27/12/20 à 14:44, gregor herrmann a écrit :
[...]
After updating to 2.5.7-1: * Accept new /etc/geoclue/geoclue.conf. * Kill /usr/libexec/geoclue-2.0/demos/agent and /usr/libexec/geoclue. * Start /usr/libexec/geoclue-2.0/demos/agent again. * Call /usr/libexec/geoclue-2.0/demos/where-am-i Result: nothing, i.e. it times out after the default 30 seconds. (redshift at this point just hangs with "Waiting for current location to become available...") /usr/libexec/geoclue is again running as user geoclue. And that's it. So "something" (with system apps? or accuracy level? or something else?) changed which breaks how at least for me geoclue has worked for a couple of years.
I reintroduced a delay where the geoclue daemon will wait for the agent to appear on the Bus if the daemon is D-Bus activated. The timeout is "dumb" and will always wait 20s even if the agent appears earlier. The timeout for the client should be 30s. Can you try to start (systemctl start geoclue) the daemon before running "where-am-i" so the agent will be connected before the 1st location request comes in?
If the problem was the accuracy, the client would get an AccessDenied or something like that.
I just retried again in my GNOME session (so gnome-shell is acting as the agent) and with the demo agent in a terminal and both are working fine, so I'm not too sure what's happening...
Can you try to modify the geoclue.service file and add Environment=G_MESSAGES_DEBUG=all to the [Service] section (and then run systemctl daemon-reload)? That should increase the logs of the daemon
Thanks, Laurent Bigonville
