Bug 506600 - Night Light does not correctly identify data source
Summary: Night Light does not correctly identify data source
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-04 18:43 UTC by toni_rocha
Modified: 2025-07-07 07:25 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
The geoclue run the locating endlessly. (40.75 KB, image/png)
2025-07-04 18:43 UTC, toni_rocha 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description toni_rocha 2025-07-04 18:43:18 UTC 
Created attachment 182961 [details]
The geoclue run the locating endlessly.

SUMMARY
The night light's GPS location service has been changed, but it continues to search endlessly for a location and doesn't pick the right time to turn it on.

STEPS TO REPRODUCE:
1. Go to "Configure Night Light..."

OBSERVED RESULT
The label "Locating..." never find the location. But the system apparently detects it, because the application works at the correct time.

EXPECTED RESULT:
The label "Locating..." should stop and show the location.

SOFTWARE/OS VERSIONS:
Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.0
Kernel Version: 6.11.0-29-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700 CPU @ 3.00GHz
Memory: 24 GiB of RAM (23,3 GiB usable)
Graphics Processor 1: Intel® UHD Graphics 630
Graphics Processor 2: llvmpipe
Manufacturer: Dell Inc.
Product Name: Vostro 3470

ADDITIONAL INFORMATION
When I run the command "systemctl status geoclue", on terminal, it shows:

geoclue.service - Location Lookup Service
     Loaded: loaded (/usr/lib/systemd/system/geoclue.service; static)
     Active: active (running) since Fri 2025-07-04 14:04:06 -03; 1h 36min ago
   Main PID: 2119 (geoclue)
      Tasks: 4 (limit: 28464)
     Memory: 12.8M (peak: 14.9M)
        CPU: 584ms
     CGroup: /system.slice/geoclue.service
             └─2119 /usr/libexec/geoclue

jul 04 14:55:08 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:00:12 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:05:16 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:10:20 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:15:24 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:20:28 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:25:32 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:30:36 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:35:28 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
jul 04 15:35:28 administrador-Neon-vostro3470 geoclue[2119]: Failed to query location: Query location SOUP error: Not Found
Comment 1 Carlos De Maine 2025-07-05 08:05:47 UTC 
seems Mozilla have shut down there geoip service.  a workaround is to use the beacondb.net service instead.  cut and past :
```
sudo tee /etc/geoclue/conf.d/99-beacondb.conf <<EOF
[wifi]
enable=true
url=https://api.beacondb.net/v1/geolocate
EOF
```
into a konsole and then `systemctl restart geoclue.service`
may be possible to script this into the kwin package