Bug 417426 - Night Color disables selected icc profile
Summary: Night Color disables selected icc profile
Status: RESOLVED DUPLICATE of bug 413134
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (show other bugs)
Version: 5.17.5
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-11 15:20 UTC by Rauros
Modified: 2020-02-11 15:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rauros 2020-02-11 15:20:54 UTC
SUMMARY
Using Night Color disables selected icc profiles and changes to default profile.

STEPS TO REPRODUCE
1. Aplly icc profile through Color Correction in System Settings.(colord-kde package may needed.)
2. Enable Night Color
3. 

OBSERVED RESULT
Night color disables applied icc profile and switches to default color profile.

EXPECTED RESULT
Night color should not interfere with icc profile.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION
Same problem doesn't happen with Gnome night light. It happens in redshift but they added preserve color option that doesn't interfere with icc profile. 
(This preserve option is not default because it causes many issues such as changing temparature disables selected icc profiles or disabling redshift through widget causes screen to go redder as well as, again, breaks icc profile, instead of disabling.)
https://github.com/jonls/redshift/issues/309

This bug also might be related with (Bug 413134 - Night colors disabled when we open gamma in settings) but i am not sure. 
https://bugs.kde.org/show_bug.cgi?id=413134
Comment 1 David Edmundson 2020-02-11 15:23:55 UTC
yeah, it's the same thing. We can't have two things control a gamma ramp at once

*** This bug has been marked as a duplicate of bug 413134 ***