Bug 420313 - Night color location detection returns the wrong location
Summary: Night color location detection returns the wrong location
Status: RESOLVED NOT A BUG
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (other bugs)
Version First Reported In: 5.18.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2020-04-19 19:36 UTC by John van Spaandonk
Modified: 2020-04-22 13:37 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John van Spaandonk 2020-04-19 19:36:30 UTC
SUMMARY


STEPS TO REPRODUCE
1. Set the time zone to Amsterdam in system settings - date & time
2. open night color module in system settings
3. 

OBSERVED RESULT
Observe longitude and lattitude that do not match with Amsterdam)
   Lattitude: 25,8295, Longitude: -80,2927

EXPECTED RESULT
I would expect to see the lattitude and longitude of Amsterdam,
About 5 and 52

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Neon
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION
This worked before but stopped working a few weeks ago. Sorry that I cannot be more specific. At the moment I use night color in manual mode. 

Another bug: Night color shows latitude 0 Longitude 0 before quickly updating it to the above reporting results.
Comment 1 Nate Graham 2020-04-20 20:09:20 UTC
Looks like the automatic location feature isn't working for you. Works okay for me though.
Comment 2 Nate Graham 2020-04-20 20:10:03 UTC
Are you behind a proxy or using a VPN or another service that might result in your IP address being geolocated far from your actual address?
Comment 3 John van Spaandonk 2020-04-22 06:31:18 UTC
Indeed Nate!
I played a bit and the setting is caused by my VPN to another time zone. I switched to manual time zone in Nightlight now and the issue seems resolved. 
Although this makes me feel a little stupid I will continue trying to create good bug reports :-)
Comment 4 Nate Graham 2020-04-22 13:37:43 UTC
No worries!