Unable to connect to GeoClue

[Fred]

Trying location provider `geoclue2'...
Using provider `geoclue2'.
Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 1000.
Unable to connect to GeoClue.
Unable to get location from provider.

I think 1.10-3ubuntu1 broke it.
I think 1.10-3 worked.
At least 1.10-2 worked. :)

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: redshift 1.10-3ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Sat Aug 15 03:01:24 2015
InstallationDate: Installed on 2013-12-26 (596 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: redshift
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jackson Doak (noskcaj)]

This appears to be fixed in the new new debian release. I will merge it in about a week if no one else takes the merge

[Jackson Doak (noskcaj)]

Can someone please take this merge? It needs to be done before release, and i have no access to a machine i can do the merge on.

[Anmar Oueja (anmar)]

Anyupdates on this guys. It is still broken and 15.10 release is drawing close.

[Jackson Doak (noskcaj)]

Marking this as high as this removes a lot of the programs functionality

[Launchpad Janitor (janitor)]

This bug was fixed in the package redshift - 1.10-5ubuntu1

---------------
redshift (1.10-5ubuntu1) wily; urgency=low

  * Merge from Debian. (LP: #1485153) Remaining changes:
    - debian/rules: Add --enable-ubuntu
    - debian/patches/retry-geoclue.patch: Retry geoclue a few times so
      redshift does not explode at startup.

redshift (1.10-5) unstable; urgency=medium

  * [8a88246] Add some changes from Laurent Bigonville
  * [ca45b49] Drop README.Debian
  * [4b34f2c] Add header to quilt patch
  * [9e854c4] Add debian/gbp.conf

redshift (1.10-4) unstable; urgency=medium

  * [c3cdd0e] Drop patch remove_autostart.patch (Closes: #791598)
  * [47e94ba] Ship appdata file in redshift-gtk.
    Thanks to Laurent Bigonville (Closes: #791600)
  * [3a6b76d] Fix reference to correct name.
    Thanks to Torquil Macdonal Sorensen (Closes: #795502)
  * [26605bd] Add redshift.desktop file entry. Needed for GeoClue activation.
    Thanks to Laurent Bigonville (Closes: #789883)
  * [536ef7e] Add dh-autoreconf to build. Drop autotools_dev from build.
    Call intltoolize to update po/ files
  * [4983734] Ship redshift.desktop file
  * [a1397f2] Add configure flag for systemd user unit dir
  * [fb6fb18] Add redshift-gtk.desktop file that got dropped off mistakenly
    in the redshift.desktop patch

 -- Jackson Doak <email address hidden> Thu, 15 Oct 2015 06:10:29 +1100

[Fred (eldmannen+launchpad)]

Using version 1.10-5ubuntu1.

It does not seem fixed.

$ redshift
Trying location provider `geoclue2'...
Using provider `geoclue2'.
Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 1000.
Unable to connect to GeoClue.
Unable to get location from provider.

[Sander (sanderth)]

Confirming that this bug is not fixed in version 1.10-5ubuntu1 (wily).
This bug is also listed on the Fedora bugtracker, for reference, see: https://bugzilla.redhat.com/show_bug.cgi?id=1214978

The quick-fix noted on that page also works for Ubuntu:
Can be fixed by adding
"[redshift]
allowed=true
system=false
users="
to /etc/geoclue/geoclue.conf

[Mohammad Anwar Shah (mohammadanwarshah)]

The bug is not fixed on 15.10 on date 2016-05-08 (May, 8) with latest version

[Daniel Stoni (stoni.ch)]

It's still the same with 16.04. Please investigate. Thank you

[Miguel Romão (romao-miguel)]

I have this bug on Ubuntu Gnome 16.04

[Jean Claveau (jean-claveau-g)]

I had the same error with 16.10 then realized that my user actually hadn't the access to geoloc service anymore. I re-enabled it in Settings -> Privacy -> Location Services.

This just occurs just after I needed a killall to end redshift so I wonder if this killing produced a something bad with the access to the geoloc.

It would be simpler if redshift could ask for Location Service activation instead of throwing an error.

[Luc Pi (oluc)]

I fully second the previous comment #13 :

- still in 16.10
- started by the session, it works perfectly
- started "by hand", it fails and throws the geoclue error
- enabling "Settings -> Privacy -> Location Services" makes it work again

There are 2 bugs (IMHO)
1. there is no reason why it would work from the session but not when started by hand
2. redshift-gtk should be more friendly about the error and suggest a solution.