Bug 419690

Summary: Night color setting doesn't extend to external monitors
Product: [Applications] systemsettings Reporter: bhaskarsmanda
Component: kcm_nightcolorAssignee: Plasma Bugs List <plasma-bugs>
Status: CONFIRMED ---    
Severity: normal CC: daniel-other+kdebug, karl, kwin-bugs-null, magnussolidus, nate, openmindead, swastiksayan2712, torokati44, vlad.zahorodnii
Priority: NOR    
Version: 5.18.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description bhaskarsmanda 2020-04-05 17:54:09 UTC 
When a second monitor is connected via HDMI, the night color setting doesn't extend to it. Have to unset "Activate Night Color", and re-set it, then it extends.


STEPS TO REPRODUCE
1. Connect HDMI monitor, observe color temperature is much higher that on notebok screen which has night color operation mode "Constant".
2. Uncheck "Activate Night Color", "Apply", check it again, "Apply".
3. Both monitors display a lowering of color temperature.

OBSERVED RESULT
Notebook display is in night color mode,  monitor connected via HDMI cable is not.

EXPECTED RESULT
Night color mode should apply to connected external monitors too.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.67.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

Upon request.
Comment 1 Daniel 2020-07-14 21:47:41 UTC 
Can confirm. If you attach an external screen, after the night color has kicked in, the color of the new screens isn't updated.
Comment 2 Magno Lomardo 2020-11-08 20:28:01 UTC 
Can confirm.

In my case the Night Color goes off immediately after the "night color tab" is no longer in focus. 

I am experiencing this on a desktop, using a NVIDIA 550ti with monitors on both HDMI and VGA ports. 
For my case, it does not matter if the monitor is the primary display or not, the one at the VGA port always get the "night color" disabled once the "night color" configuration tab loses focus.
Comment 3 Aaron Wolf 2024-03-04 04:20:46 UTC 
*** Bug 481269 has been marked as a duplicate of this bug. ***