1906311 - [snap/ Ubuntu] Your precise location could not be determined error is displayed on Google Maps and Bing Maps

Status: NEW

(Core :: DOM: Geolocation, defect)

Description

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: image.png

Found in

• 129.0a1 (2024-07-03) - snap

Affected versions

• 129.0a1 (2024-07-03) - snap
• 128.0 - snap
• 127.0.2 - snap
• 115.13.0esr-2 - snap

Tested platforms

• Affected platforms: Ubuntu 24, Ubuntu 23 (snap)
• Unaffected platforms: macOS, Windows

Steps to reproduce

1. Install a Firefox snap build.
2. Open Firefox snap and verify that the location works on Bing and Google Maps.

Expected result

• Current location is displayed.

Actual result

• The Your precise location could not be determined. error is displayed.

Regression range

• I don’t think we can search regressions on a Snap package.

Additional notes

• Attached a screenshot.
• This issue does not reproduce with 129.0a1 (2024-07-03) tar.bz2, 128.0b9 flatpak, Firefox.deb 129.0a1 (2024-07-03).
• In the Firefox 128.0b9 flatpack build, the location is only displayed when requested a second time on Google Maps in a new session. The first time requesting location, it will show the Your precise location could not be determined error. This behavior also occurs in older builds (e.g., 124.0b6).
• The Browser Geolocation test from https://mylocation.org/ correctly shows the Longitude and Latitude on Snap builds.
• On Debian 12, the Firefox snap 129.0a1 (2024-07-03) works on Google Maps but only if the location is requested a second time in a new session. This also happens in the 128.0b9 Snap Firefox build.
• I don't think this has something to do with bug 1905717 since it happens on all snap builds.

Comment 1

[Kagami Rosylight [:saschanaz] (they/them)]

This somehow slipped my radar after setting the dependency 😬, sorry!

We need to use the same pref geo.provider.geoclue.mls_fallback_timeout_ms (but maybe with different name?) for Portal too as we figured 10sec is already too long. We use 12sec for Portal right now.

Comment 2

[Kagami Rosylight [:saschanaz] (they/them)]

Hmm actually, it works for me, so maybe Portal has at least better error behavior?

If you run navigator.geolocation.getCurrentPosition(console.log, console.error), do you see an error? If not, how high the GeolocationPosition.coords.accuracy value is?

Comment 3

[Alexandru Trif, Desktop Test Engineering [:atrif]]

I don't see any error and the accuracy is now 1676.6879712869427. I know that last time was much higher over 200000.

Comment 4

[Alexandru Trif, Desktop Test Engineering [:atrif]]

(In reply to Alexandru Trif, Desktop QA [:atrif] from comment #3)

I don't see any error and the accuracy is now 1676.6879712869427. I know that last time was much higher over 200000.

Sorry for the spam, I forgot that last time I was testing it with a Wi-Fi hotspot. Accuracy is 1676.6879712869427 when connected to my router's WiFi and 203208.91640780002 when connected to a WiFi hotspot.