The new version with the change landed in Ubuntu since
** Changed in: geoclue-2.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799339
Title:
** Changed in: geoclue-2.0 (Ubuntu Cosmic)
Importance: Undecided => Low
** Changed in: geoclue-2.0 (Ubuntu Cosmic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since the package failed verification, I am removing it from cosmic-
proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799339
Title:
GeoClue times out on start
To manage notifications about
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799339
Title:
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 removed: verification-needed-cosmic
** Tags added:
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
done
** Description changed:
* 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
** Changed in: geoclue-2.0 (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799339
Title:
GeoClue times out on start
To manage notifications about
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
** Changed in: geoclue-2.0 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799339
Title:
GeoClue times out on start
To manage notifications about
** Description changed:
+ * 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
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!
--
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)
** Bug watch added: Debian Bug tracker #908489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908489
** Also affects: geoclue-2.0 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908489
Importance: Unknown
Status: Unknown
--
You received this bug notification
14 matches
Mail list logo
