515558 2026-02-05 16:38:37 +0000 Day/Night time switch happens at the end of sunrise/sunset 2026-02-19 12:26:18 +0000 1 1 2 Applications systemsettings kcm_nighttime 6.5.5 Other Linux RESOLVED DUPLICATE 511973 https://bugs.kde.org/show_bug.cgi?id=515533 NOR normal --- 1 agurenko plasma-bugs-null maciej.stanczew vlad.zahorodnii walter.von.entferndt 0 oldest_to_newest 2491601 0 agurenko 2026-02-05 16:38:37 +0000 SUMMARY I absolutely love the Day/Night time switch and I've been waiting for it for a very long time, but after using it for a while, the fact that switch occurs at the end of the sunrise/sunset puts it in a wrong time. At least here in southern Germany at "Sunset starts at <time>" it's already dark. There is already another request for the offset here https://bugs.kde.org/show_bug.cgi?id=515533, which is also valid, but I still think that even in a current form the switch should occur on the start of the event and not at the end, because there is 35-40 minute difference there for me. Maybe give it a toggle (Start, End, middle point(?)) STEPS TO REPRODUCE 1. Set Day/Night cycle based on device location 2. Wait until official sunset time OBSERVED RESULT Nothing happens at the official sunset time, instead it happen at "Sunset ends at <time>" EXPECTED RESULT I strongly feels it should happen at the beginning of the event, unless it's different in other parts of the world, then it should be configurable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 43 KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 ADDITIONAL INFORMATION 2492201 1 walter.von.entferndt 2026-02-07 14:20:19 +0000 merge request is pending on invent.kde.org (GitLab) 2496185 2 maciej.stanczew 2026-02-19 12:23:18 +0000 I believe the late sunset part should be covered by bug 511973. 2496186 3 agurenko 2026-02-19 12:25:26 +0000 (In reply to Maciej Stanczew from comment #2) > I believe the late sunset part should be covered by bug 511973. Yes, that seems to cover same issue 2496187 4 agurenko 2026-02-19 12:26:18 +0000 *** This bug has been marked as a duplicate of bug 511973 ***