** Changed in: geoclue-2.0 (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location a
@Sebastien Bacher Just doing an occasional Python GET request to the
same URL others are using:
https://location.services.mozilla.com/v1/geolocate?key=geoclue
Alternatively, calling that URL in a browser. It works occasionally, but
mostly it just returns a 403. The JSON string:
{"error":{"errors":
@osomon any news on the key request for Ubuntu ? I'm hitting usage
limits randomly with the generic "geoclue" key which makes redshift not
work sometimes. It's the same error as @heap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclu
@Robin, how do you trigger the issue exactly? could you describe what
website you try and what error you get?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue
Update: key has not worked for several days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 pac
Update: key is working again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Can confirm that this stopped working 2 days ago. But when called
manually from a script:
https://location.services.mozilla.com/v1/geolocate?key=geoclue
Can someone clarify: Is the shared "geoclue" key likely to come to life
again, and if so is there any timeline?
--
You received this bug notif
For the record, back in April 2019 Canonical requested a separate MLS
API key to use in geoclue in Ubuntu, and the request was initially
acknowledged, but then it was put on hold on Mozilla's end and we never
heard back from them, despite a couple of follow-up e-mails.
>From the discussion in the
Updated upstream bug:
https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/136, opened 20
OCT 2020
Looks like the Mozilla MLS maintainer has proposed to deprecate the
default key in order to force downstreams to get their own keys:
>From the linked bug:
"My proposal is to deprecate the defaul
(seems like GNOME got it somehow resolved for now,
https://gitlab.gnome.org/Teams/Board/issues/97 mentions it)
** Bug watch added: gitlab.gnome.org/Teams/Board/issues #97
https://gitlab.gnome.org/Teams/Board/issues/97
--
You received this bug notification because you are a member of Desktop
P
Is anyone still getting the issue? It seems to work fine here now, GNOME
was also discussing the issue so maybe they got the quota increased?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.ne
** Changed in: geoclue-2.0 (Ubuntu)
Importance: Undecided => High
** Changed in: geoclue-2.0 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: geoclue-2.0 (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member
Same.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}
Hopefully we can get Mozilla to u
I tried it again just now (roughly around the same time of day I tried
this previously):
$ curl https://location.services.mozilla.com/v1/geolocate?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
I tried it around 02:00 UTC on 25 April so the daily limit was probably
reset by the time you tested it. I did check around and came across this
issue on geoclue's GitLab
https://gitlab.freedesktop.org/geoclue/geoclue/issues/101
The geoclue key probably has a high daily limit but it's probably bei
Tested just now (25 April, 10:00 UTC) and a query to the service with
the "geoclue" key returns a valid location. I wonder if someone already
increased the quota for that key and the issue can be considered solved,
or if it's just a lucky coincidence and the daily limit was reset before
I tried.
I
I would imagine that the currently shipped API key of "geoclue" is some
kind of universal default. Now that the use of keys is apparently being
monitored and limited, perhaps it would be possible for Ubuntu to
register its own key, and then ship that with this package?
--
You received this bug no
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: geoclue-2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/b
18 matches
Mail list logo
