redshift does not get complete response from geoclue on initial startup/query

Bug #1060645 reported by Clint Byrum
44
This bug affects 10 people
Affects Status Importance Assigned to Milestone
geoclue (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

In ubuntu 12.10 beta2, I try to start redshift and get this:

$ redshift
Started Geoclue provider `Geoclue Master'.
Using provider `geoclue'.

** (process:19970): WARNING **: Could not get location, 3 retries left.

** (process:19970): WARNING **: Could not get location, 2 retries left.

** (process:19970): WARNING **: Could not get location, 1 retries left.

** (process:19970): WARNING **: Provider does not have a valid location available.
Unable to get location from provider.

##
This repeats over and over. But, if I kill geoclue-master:

$ redshift
Started Geoclue provider `Geoclue Master'.
Using provider `geoclue'.
According to the geoclue provider we're at: 34.07, -118.35
Using method `randr'.
^C
##
I have done some debugging, and latitude actually comes back (34.07) but not longitude, it stays at 0.

During this time, geoclue-test-gui works fine, so I imagine this is only in the non-async calls.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: geoclue 0.12.99-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.24~smb2-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Tue Oct 2 22:37:07 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: geoclue
UpgradeStatus: Upgraded to quantal on 2012-09-06 (26 days ago)

Revision history for this message
Clint Byrum (clint-fewbar) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in geoclue (Ubuntu):
status: New → Confirmed
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Sorry no Jonathan, this is not a duplicate of that. I've done some deep internal debugging. This is the case where geoclue *is* up, but is giving back only half of a response. They're related, no doubt, but not the same.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.