Bug 453734

Summary: Night Color (kcm_nightcolor) Longitude and Latitude is not determined automatically by its Location Service
Product: [Applications] systemsettings Reporter: raguse <contactbay>
Component: kcm_nightcolorAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: minor CC: kwin-bugs-null, nate
Priority: NOR    
Version: 5.24.5   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description raguse 2022-05-13 10:24:36 UTC
SUMMARY
In Systemstettings > Display and Monitor > Night Color (kcm_nightcolor) when using 'Sunset and Sunrise at current location" it does not automatically acquire Latitude and Longitude information anymore since upgrade to Frameworks 5.93 / Plasma 5.24.5. Therefore, Night Color is starting at wrong times and can't be determined automatically. 
I suppose it's an issue of Mozilla Location Service since GPS is not used in my case. Firewall is also tuned off. 

Error Message: Failed to load GeolocationProvider: "/usr/lib/qt/plugins/plasma/geolocationprovider/plasma-geolocation-gps.so"

This used to work in FW 5.92 / Plasma 5.24.4 according to my tests. I also tried the latest KDE Neon release iso 20220512 in a Virtual Machine and it's also not acquiring location. 

There is a similar bug report but unrelated I assume https://bugs.kde.org/show_bug.cgi?id=453242

STEPS TO REPRODUCE
1. Open System Settings and Navigate to Night Color Settings
2. Choose 'Sunset to Sunrise at current location"

OBSERVED RESULT
Longitude and Latitude remain 0° 

EXPECTED RESULT
System detects Longitude and Latitude automatically and adjust Night Color start and end times automatically

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.6-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4210Y CPU @ 1.50GHz
Memory: 7,6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4200

ADDITIONAL INFORMATION
There is a similar bug report but unrelated I assume https://bugs.kde.org/show_bug.cgi?id=453242
Comment 1 Nate Graham 2022-05-13 14:55:25 UTC
Looks like the same issue, yeah.

*** This bug has been marked as a duplicate of bug 453242 ***