GeoClue times out on start

Bug #1799339 reported by Olek Wojnar on 2018-10-23
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
geoclue-2.0 (Debian)
Fix Released
Unknown
geoclue-2.0 (Ubuntu)
High
Unassigned
Cosmic
Undecided
Unassigned

Bug Description

* Impact

On some configs registration to the geoclue service might fail because the agent is started too late/after the registration timeout

* Test case

log into an Ubuntu/GNOME session and check that the geolocation feature is working (used to adjust the timezone for example)
- log into your Ubuntu/GNOME session
- go to gnome-control-center, enable the geolocation and automatic timezone adjustement options
- reboot to gdm (without login in)
- go to a vt
- change the timezone to be not matching the actual location
- go back to gdm and log in

-> verify that the timezone get adjusted automatically to match your real location one

or from the original report
- install xubuntu
- install redshift and start it/configure it to change your screen profile/colors at night
- log into your xfce session at a time configured to color the screen red

-> the screen color should change according to the calibration

* Regression potential

The change is only to increase a timeout delay

-----------------------

Due to an upstream bug (https://gitlab.freedesktop.org/geoclue/geoclue/issues/84) GeoClue times out upon startup and certain applications (such as Redshift) do not function as intended. This has already been fixed upstream (version 2.5.0) and that version is available in Debian. Please pull the latest Debian version to fix this bug.

Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that seems a candidate for a fix backport but could you describe with some extra details what version of Ubuntu you are using, what you are doing and what problem you hit? (you mentioned redshift, where do you use it and how?)

Changed in geoclue-2.0 (Ubuntu):
status: New → Triaged
importance: Undecided → High
Olek Wojnar (olekw) wrote :

Sebastien, I'm on Xubuntu 18.10 and I'm using the redshift package through redshift-gtk. As described in the upstream bug, the problem occurs on login when redshift attempts to start automatically and fails due to the geoclue timeout.

Please let me know if there's anything else that you need!

description: updated
Changed in geoclue-2.0 (Ubuntu):
status: Triaged → Fix Committed
Olek Wojnar (olekw) on 2018-10-31
Changed in geoclue-2.0 (Debian):
importance: Unknown → Undecided
status: Unknown → New
importance: Undecided → Unknown
status: New → Unknown
Steve Langasek (vorlon) wrote :

Please flesh out this SRU test case so that it can be clearly followed by someone unfamiliar with xfce and redshift.

(Likewise, I don't know what to expect on an Ubuntu session wrt timezone adjustment. Given that I have yet to find any option to let me manually configure timezones in recent GNOME, to have the session start to change timezone settings with no way to override through the UI sounds like it would constitute a regression for some users.)

Changed in geoclue-2.0 (Ubuntu):
status: Fix Committed → Incomplete
Changed in geoclue-2.0 (Debian):
status: Unknown → Fix Released
Sebastien Bacher (seb128) wrote :

done

description: updated
Changed in geoclue-2.0 (Ubuntu):
status: Incomplete → Fix Committed

Hello Olek, or anyone else affected,

Accepted geoclue-2.0 into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/geoclue-2.0/2.4.12-2ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in geoclue-2.0 (Ubuntu Cosmic):
status: New → Fix Committed
tags: added: verification-needed verification-needed-cosmic
Beacker (beacker) wrote :

Hello Brian.

The package 2.4.12-2ubuntu2 does not fix the bug for me: `geoclue.service` becomes inactive 5 seconds after being started.

Unlike package 2.4.12-2ubuntu1, launching Redshift will not start `geoclue.service`.

tags: added: verification-failed-cosmic
removed: verification-needed-cosmic
Sebastien Bacher (seb128) wrote :

K, so the issue there was probably not the one pointed in the description/that commit. Likely not going to be fixed in cosmic then

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

Other bug subscribers

Remote bug watches

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