1342466 - geolocation stopped working

Status: RESOLVED DUPLICATE of bug 1232995

(Core :: DOM: Geolocation, defect)

Description

[Dutch Kind]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170126000000

Steps to reproduce:

Some time ago, probably a few weeks, suddenly sites like tomtom drive, that need geolocation, return a message that no location was found. I get this popup to allow it, confirm, and nothing happens, just an error message about location.

I checked in chromium and the location is given within a fraction of a second


Actual results:

No geo location


Expected results:

current location should show up on website

Comment 1

[Michelangelo De Simone [Offline] [:mds]]

I'm afraid this might due to a well known situation with one of our providers.
Would you please try to reproduce the problem by using the Aurora (WebDeveloper) edition of Firefox?

You can download it from here: https://www.mozilla.org/en-US/firefox/developer/all/

Comment 2

[Dutch Kind]

I tried it and at least I get a location again, no error messages. But no very accurate. Some months ago, before it stopped working, it would give a reasonably exact location at village level, then it changed to the provincial capital, roughly 60 km from where I live, but now, with this developer version it gives me the location of the country's capital, about 400 km away! I think it takes the official address of my ISP, so it is not very useful, but at least better than in the current stable.

Comment 3

[Andrew Overholt [:overholt]]

(In reply to Michelangelo De Simone [:mds] from comment #1)
> I'm afraid this might due to a well known situation with one of our
> providers.

Can you elaborate, Michelangelo? Does comment 2 confirm this?

Comment 4

[Michelangelo De Simone [Offline] [:mds]]

(In reply to Andrew Overholt [:overholt] from comment #3)

> Can you elaborate, Michelangelo? Does comment 2 confirm this?

I'm rather positive this is due to the well known problem of the release geo provider: unfortunately there is no real, ultimate, fix for this other than "harmonizing" the provider situation, and that's what we're doing in bug 1341897.

Comment 5

[Andrew Overholt [:overholt]]

(In reply to Michelangelo De Simone [:mds] from comment #4)
> (In reply to Andrew Overholt [:overholt] from comment #3)
> 
> > Can you elaborate, Michelangelo? Does comment 2 confirm this?
> 
> I'm rather positive this is due to the well known problem of the release geo
> provider: unfortunately there is no real, ultimate, fix for this other than
> "harmonizing" the provider situation, and that's what we're doing in bug
> 1341897.

Gotcha, thanks.

Comment 7

[Michelangelo De Simone [Offline] [:mds]]

Sylvestre, could you please check the dasboard to confirm this is related to the quota problem?

Comment 8

[Michelangelo De Simone [Offline] [:mds]]

Dutch, while we check this, would you please be so kind to try to reproduce this again on the normal release?

Comment 9

[Sylvestre Ledru [:Sylvestre]]

Not a quota issue, by far.

Comment 10

[Dutch Kind]

(In reply to Michelangelo De Simone [Offline] [:mds] from comment #8)
> Dutch, while we check this, would you please be so kind to try to reproduce
> this again on the normal release?

Sorry, missed this one.

In the mean time, geolocation gives some location, which varies. It's always in the same province but can differ from day to day of which town or city is shown, but usually about 60km from my actual location. At least no more error messages, so only accuracy improvement would be nice.