Le 07/06/18 à 02:46, James Tocknell a écrit :
Dear Maintainer,
The update to 2.4.10-1 causes redshift to immediately crash, with the error:
Failed to connect to GeoClue2 service:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' disallowed, no
agent for UID 1000
Which desktop environment are you using? Because it's usually the DE
that is supposed to implement this.
Starting the agent in the demo package manually appears to make no difference.
Additionally, I tried to use the where-am-i demo, which produced the same error
(again with the agent started).
I think the cause is this change referred to in the upstream changelog:
"Refuse location access if no app-auth agent is registered. This fixes a
security hole where an app requests location access before the agent gets to
register itself and we end up giving out locaiton access even though user has
disabled it."
Can the change be reverted until the agent works?
Well, I don't know to be honest, the demo agent is a demo, that should
be implemented in the DE itself. Only GNOME (and I think enlightenment)
are implementing this ATM and it could take a long time to be
implemented in the others. (Don't know if there are even feature
requests open)
Couldn't the geolocation feature be disabled in redshift? Or couldn't
the geoclue config file be adjusted to allow redshift to work without
asking the agent?
FYI, I make the report critical so that the change doesn't migrate to testing,
feel free to drop the severity if you think that's appropriate.
