Bug 503658 - Night color / Night light asks about unsaved changes even though nothing was changed
Summary: Night color / Night light asks about unsaved changes even though nothing was ...
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (other bugs)
Version First Reported In: 6.3.4
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-02 11:27 UTC by Tobias Zwick
Modified: 2025-07-25 10:41 UTC (History)
2 users (show)

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


Attachments
video that showcases the issue (380.05 KB, video/webm)
2025-05-02 11:27 UTC, Tobias Zwick
Details
bug not resolved (131.80 KB, image/png)
2025-07-24 16:10 UTC, Tobias Zwick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Zwick 2025-05-02 11:27:18 UTC
Created attachment 180875 [details]
video that showcases the issue

SUMMARY
When one haven't entered the night color settings for a bit, on exiting these settings, one is asked about saving changes even if one didn't change anything.

STEPS TO REPRODUCE
1. Have night light on.
2. Wait for some time until reentering night light settings. (Unknown by how much - 10 minutes? 10 hours? Until geolocation changed a bit?) 
2. Reenter night light settings
3. Exit night light settings (e.g. switch to a different item in the navigation)

OBSERVED RESULT
Prompt that asks about unsaved changes is shown when exiting the night color screen.

EXPECTED RESULT
Prompt is only shown when the user made changes.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 42

ADDITIONAL INFORMATION
Might be related: https://bugs.kde.org/show_bug.cgi?id=477928
Comment 1 Nate Graham 2025-05-02 16:01:08 UTC
This is fixed for Plasma 6.4!
Comment 2 Tobias Zwick 2025-05-02 16:15:32 UTC
Nice!
Comment 3 Tobias Zwick 2025-07-24 16:10:38 UTC
I am on Plasma 6.4.3 now and can not confirm that the bug has been fixed.
Comment 4 Tobias Zwick 2025-07-24 16:10:50 UTC
Created attachment 183496 [details]
bug not resolved
Comment 5 Nate Graham 2025-07-25 10:41:13 UTC
Seems to be fixed again in git master.