Bug 444524 - Redshift shouldn't override a custom color profile if disabled
Summary: Redshift shouldn't override a custom color profile if disabled
Status: REPORTED
Alias: None
Product: plasma-redshift-control
Classification: Unmaintained
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-28 08:37 UTC by Avamander
Modified: 2021-10-28 08:37 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Avamander 2021-10-28 08:37:27 UTC
SUMMARY
I have a custom ICC color profile for my display. But having redshift running or even going near its control resets the profile to the default one. To the user it seems that shortly after applying an iCC profile, it unsets itself.

STEPS TO REPRODUCE
1. Set a custom color profile
2. Have redshift running but disabled, or not running and hover over the control
3. Wrong color profile gets set

OBSERVED RESULT
Color profile is reset to default, colord is not aware (UI state is inconsistent)

EXPECTED RESULT
When a custom color profile is set, redshift restores that custom color profile if its disabled. Alternatively, it refuses to touch the profiles if it detects a custom one.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2