Summary: | Transition to night color starts way too early in "Current Location" mode | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | jvanh1983 |
Component: | kcm_nightcolor | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | dellfirmware, igarcia, isma.af, kwin-bugs-null, nate, sanjayswain450 |
Priority: | NOR | ||
Version: | 5.27.5 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | night light |
Description
jvanh1983
2023-06-29 18:02:18 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. 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? No, I'm not using anything like that. Strange is that it DOES work when I set my location manually. The geolocator should print the location it calculated. Can you verify that it's correct? 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! (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. Created attachment 162387 [details]
night light
(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 (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) Also probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=469730 *** This bug has been marked as a duplicate of bug 469730 *** |