Bug 471639 - Transition to night color starts way too early in "Current Location" mode
Summary: Transition to night color starts way too early in "Current Location" mode
Status: RESOLVED DUPLICATE of bug 469730
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (show other bugs)
Version: 5.27.5
Platform: Manjaro Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-29 18:02 UTC by jvanh1983
Modified: 2023-11-05 19:32 UTC (History)
6 users (show)

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


Attachments
night light (734.36 KB, image/png)
2023-10-17 21:44 UTC, Ivan Garcia
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jvanh1983 2023-06-29 18:02:18 UTC
SUMMARY
***
When I set 'switching times' to 'sunset and sunrise at current location' the transition to night colors starts well before the starting time mentioned on the night color settings page.
It does seem to work as expected with the option 'sunrise and sunset at manual location'.
***

STEPS TO REPRODUCE
1. Location: latitude 51.81 longitude 5.83
2. To have Windows keep showing the correct time I did this:
timedatectl set-local-rtc 1 --adjust-system-clock
3. Output of timedatctl:
Local time: Th 2023-06-29 19:50:42 CEST
Universal time: Th 2023-06-29 17:50:42 UTC
RTC time: Th 2023-06-29 19:50:45
Time zone: Europe/Amsterdam (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: yes
5. In night color settings, set ' switching times'  to 'sunset and sunrise at current location' and location as mentioned above.

OBSERVED RESULT
Transition to night color starts 1.5-2 hours early. Setting location to manual, the transition starts at about the right time.

EXPECTED RESULT
Setting ' switching times'  to either 'sunrise and sunset at current location' and 'sunrise and sunset at manual location' both result in the transition to night color starting at the right time.

SOFTWARE/OS VERSIONS
Windows: 10 Home Edition
DE Plasma: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
N/A
Comment 1 Laosom 2023-07-03 18:01:55 UTC
I also experience this weird behaviour with the "sunset and sunrise at current location" setting on EndeavourOS (Plasma 5.27.6) and Debian Bookworm (Plasma 5.27.5) as well. It starts about 2 hours before and stops about 2 hours later. 
If I choose "sunrise and sunset at manual location" with my location coordinates , it starts and stops in the right time.
I doublechecked my locale and timezone settings, it's correct. 
In Plasma 5.24.7 LTS Night Color works well.
Comment 2 Nate Graham 2023-09-14 18:54:32 UTC
Seems like maybe the geolocation service has gotten your location wrong. Are you by any chance using a VPN or anything else that could cause your IP address to get geolocated to somewhere you're not?
Comment 3 jvanh1983 2023-09-18 16:24:49 UTC
No, I'm not using anything like that. Strange is that it DOES work when I set my location manually.
Comment 4 Nate Graham 2023-09-18 19:18:23 UTC
The geolocator should print the location it calculated. Can you verify that it's correct?
Comment 5 Bug Janitor Service 2023-10-03 03:46:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Ivan Garcia 2023-10-17 21:44:13 UTC
(In reply to Nate Graham from comment #4)
> The geolocator should print the location it calculated. Can you verify that
> it's correct?

It calculates the location correctly. It also shows the times where it is going to change color accurately as well. The issue is that it does not honor the settings. As everyone stated here, if you set it to "manual" night light works as expected.
Comment 7 Ivan Garcia 2023-10-17 21:44:54 UTC
Created attachment 162387 [details]
night light
Comment 8 Ivan Garcia 2023-10-17 21:47:03 UTC
(In reply to Ivan Garcia from comment #6)
> (In reply to Nate Graham from comment #4)
> > The geolocator should print the location it calculated. Can you verify that
> > it's correct?
> 
> It calculates the location correctly. It also shows the times where it is
> going to change color accurately as well. The issue is that it does not
> honor the settings. As everyone stated here, if you set it to "manual" night
> light works as expected.

It does not show on the screenshot but  night color is active (4500k) even though it was only 5:01PMEST
Comment 9 Sanjay Swain 2023-11-05 02:28:51 UTC
(In reply to Ivan Garcia from comment #8)
> (In reply to Ivan Garcia from comment #6)
> > (In reply to Nate Graham from comment #4)
> > > The geolocator should print the location it calculated. Can you verify that
> > > it's correct?
> > 
> > It calculates the location correctly. It also shows the times where it is
> > going to change color accurately as well. The issue is that it does not
> > honor the settings. As everyone stated here, if you set it to "manual" night
> > light works as expected.
> 
> It does not show on the screenshot but  night color is active (4500k) even
> though it was only 5:01PMEST


Is it still a issue? And if it is please can you send the output of following commands:
> qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect
and 
> qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect | awk '/Time/ {print $1, strftime("%T", $2)
Comment 10 Sanjay Swain 2023-11-05 02:29:22 UTC
Also probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=469730
Comment 11 Ismael Asensio 2023-11-05 19:32:55 UTC

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