https://bugs.kde.org/show_bug.cgi?id=493699

Ismael Asensio <isma...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |isma...@gmail.com

--- Comment #14 from Ismael Asensio <isma...@gmail.com> ---
I've been researching a bit on the topic, since I've been also affected by this
issue (Kubuntu 24.10 base, Qt 6.8.1, KDE master).

After the downfall of Mozilla Location Service (MLS) (in which most FOSS
location services were based on). Since then, we've moved to QtPositioning,
which for our use case, acts mostly a layer on top of geoclue. At the same
time, geoclue moved from using MLS as a default provider based on Wi-Fi
networks to no default service
(https://gitlab.freedesktop.org/geoclue/geoclue/-/merge_requests/184). 

This means that the issue is a bad configuration of GeoClue's settings, which
is now mostly up to the distribution: arch opted to use the Google services
with a custom API key
(https://gitlab.archlinux.org/archlinux/packaging/packages/geoclue/-/commit/561b66e7e965f5a2e9f5b0597367243d43bbfa0f),
while others such as NixOs (https://github.com/NixOS/nixpkgs/issues/321121) are
leaning into beaconDB (https://beacondb.net/). The version on my system
(Kubuntu 24.10) stills point to the Mozilla services, which explain why it
fails.

>From a user POV, as a workaround, one can restore the functionality by editing
the `/etc/geoclue/geoclue.conf` file, for example with this (or a different
provider url):
[wifi]
enable=true
url=https://api.beacondb.net/v1/geolocate

I also had to enable the location service access using `gsettings set
org.gnome.system.location enabled true`. 

On our KDE side, I think we need to improve the integration with the geoclue
service (as we are going to increasingly use it), so we can let the users set
or at least know about the settings, and the error state to show in the UI. I
still haven't been able to get an error message or even a state change from
QtPositioning when the service is failing.

Also, it is no longer true that geoclue uses GeoIP for the location
(https://gitlab.freedesktop.org/geoclue/geoclue/-/merge_requests/184/diffs?commit_id=6ec21c1e9e6b82ae0ea629ccc0acdd5c088e487b).
We should update this info on the KCM, ideally with the actual provider the
user's sending packages to.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to