1904291 - navigator.geolocation.getCurrentPosition fails with Google API key error on OpenSUSE

Status: RESOLVED MOVED

(Core :: DOM: Geolocation, defect)

Description

[promeneur]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0

Steps to reproduce:

Operating System: openSUSE Tumbleweed 20240621
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

go to openstreetmap.org or G maps

ask for home localization

Actual results:

firefox does not get the home localization.

with G maps we get a message saying getting the home localization fails.

no problem with Chrome.

Expected results:

firefox get the home localization and centers the map on the home and zooms on it.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Kagami Rosylight [:saschanaz] (they/them) (OOO until 2024-10-06)]

Hi promeneur, thanks for the report. Is this issue something new or have you been getting the same issue for a while?

Comment 3

[Kagami Rosylight [:saschanaz] (they/them) (OOO until 2024-10-06)]

I can confirm this on WSL2 OpenSUSE. Chrome works on the same installation. From NetWorkGeolocationProvider.sys.mjs, we get "API key not valid. Please pass a valid API key." from Google, and we get TypeError by accessing result.location.lng where result.location is undefined.

The flatpak distribution doesn't have this problem, so I think this is something with OpenSUSE's own distribution.

Comment 4

[promeneur]

(In reply to Kagami Rosylight [:saschanaz] (they/them) from comment #2)

Hi promeneur, thanks for the report. Is this issue something new or have you been getting the same issue for a while?

It is something new.

Comment 5

[promeneur]

I sent a report to openSUSE

see https://bugzilla.opensuse.org/show_bug.cgi?id=1226821

Comment 6

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Kagami, is there anything we can/should do on our end? If this is something with OpenSUSE's own distribution, I believe we can close as invalid.

Comment 7

[Kagami Rosylight [:saschanaz] (they/them) (OOO until 2024-10-06)]

I think we can't do much here other than having conversation with openSUSE to get the configuration right, which can happen outside this bug.