SUMMARY I want to manually control when night color is activated. The closest I have been able to get is: 1. In System settings -> Display and monitor -> Night color, set activation time to "Always on". 2. In the panel, add a Night color control plasmoid. 3. Click the plasmoid when I want to turn night color on or off. This has worked so far, except for activating night color on every login, which is not a huge problem because it only happens after rebooting for kernel upgrades. However, tonight night color is inhibited by some unknown thing and forging magic cookies to "qdbus org.kde.KWin /ColorCorrect org.kde.kwin.ColorCorrect.uninhibit" doesn't enable it. I could continue fighting the inhibition system, or try adding a new DBus interface to show the inhibitor list, but instead of adding workarounds to workarounds I have a feature request: add a manual mode, which ignores the inhibitor system entirely and just features an on/off switch in the panel. Remembering the last status and re-applying that at login (instead of always activating it) would be a bonus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1
A better way is to set it to "Always on" in the KCM and then toggle it on and off, you can either click on the system tray applet, or set and use a global shortcut.
(In reply to Nate Graham from comment #1) > A better way is to set it to "Always on" in the KCM and then toggle it on > and off, you can either click on the system tray applet, or set and use a > global shortcut. Does the system tray applet bypass the inhibition system? Because that is not documented, and if not I don't see how that is different from what I said I'm already doing, which doesn't work because of the inhibition system.
I believe so. Can you try it out and see?
It's now been a couple of weeks, including a Plasma upgrade to 5.20.0, and I have not seen night colour be permanently inhibited again. Using the plasmoid in the panel has worked the entire time. Maybe my original problem was a one-time bug.
That would be a happy ending indeed. :) Glad it's working for you now.