STEPS TO REPRODUCE 1. open Night Color KCM 2. close System Settings without changing anything 3. OBSERVED RESULT the save/discard prompt shows up EXPECTED RESULT System Settings closes SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Graphics Platform: Wayland
Can confirm. The problem appears to be that the "Switching times" combobox gets reset at launch, changing its value and causing the KCM to enter a dirty state immediately.
Looks like the currentIndexChanged() on the combobox gets called too early
For some reason, this problem doesn't appear in kcmshell6. Only in systemsettings. When running under systemsettings, the onActiveChanged connection on kcm.nightColorSettings never gets called, while it does happen under kcmshell6. I have no idea why (yet).
I have a hack solution for this, but I don't feel good about ignoring such a perplexing underlying problem. Do you think it's worth making an MR for the hack?
Depending on how difficult it would be to fix in a way you consider more correct, it might be worth submitting your hack patch as an RFC to stimulate discussion around the subject.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3050
(In reply to Bharadwaj Raju from comment #3) > For some reason, this problem doesn't appear in kcmshell6. Only in > systemsettings. > > When running under systemsettings, the onActiveChanged connection on > kcm.nightColorSettings never gets called, while it does happen under > kcmshell6. I have no idea why (yet). This looks like https://invent.kde.org/plasma/systemsettings/-/merge_requests/258 The signal/slot is broken in systemsettings
*** Bug 476927 has been marked as a duplicate of this bug. ***
Fixed by https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3580