On 7 June 2018 at 18:41, Laurent Bigonville <bi...@debian.org> wrote: > 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.
None, I start up the necessary programs via my WM (awesome). I was planning on adding the agent to my startup, but it fails to work. > >> 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? The geolocation can be disabled, but that loses a far bit of the functionality of redshift (and doesn't solve the actual problem of programs being unable to get the current location due to a non-working agent). I've tried adding redshift (and the where-am-i demo) to the config (which would have been a nice workaround, preferable to just downgrading), but that didn't appear to work either (both with and without the agent running). The agent is added to the xdg startup dir, so presumably it's supposed to function when there's no other agent? Should I create a bug on the upstream tracker about the agent appearing not to work, and post the url here? > > >> 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. > > > -- Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It isn't good enough for Tim Berners-Lee, and it isn't good enough for me either. For more information visit http://www.gnu.org/philosophy/no-word-attachments.html. Truly great madness cannot be achieved without significant intelligence. - Henrik Tikkanen If you're not messing with your sanity, you're not having fun. - James Tocknell In theory, there is no difference between theory and practice; In practice, there is.
