https://bugs.kde.org/show_bug.cgi?id=412943
Bug ID: 412943
Summary: Use System Monitor Profile checkbox attributes wrong
profile to screens, breaking color management
Product: krita
Version: unspecified
Platform: Other
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: tysont...@gmail.com
Target Milestone: ---
When the checkbox:
Configure Krita -> Color Management -> [ ] Use system monitor profile
is checked...
Krita is expected to automatically attribute color profiles set in the OS's
Color Management panel to each screen accordingly. However, in multi-screen
scenarios, it sometimes attributes profiles to the wrong displays.
#########
The problem appears to be:
The screen list underneath the checkbox:
Screen 1:
Screen 2:
...
Krita gets this list from the system's Display settings panel. For KDE Plasma,
Screen 1 is the "Primary" screen set in Plasma's Display settings. For Windows
and Gnome, Screen 1 is the display plugged into the connector with highest
priority.
But when it comes to actually applying the profiles, the top-left screen is
always #1. This often cause profiles to be attributed to the wrong displays,
breaking color accuracy in a color managed workflow.
#########
Workaround:
A) For dual screen, manually adding 2 profiles using the "Folder" icon below,
assign them in reversed order to what the "Use system monitor profile"
checkbox's automatically does.
B) KDE Plasma only: Make the top-left display "Primary".
I have no idea how we deal with this issue if we had more than 2 displays. :P
#########
Notes:
I think this is the exact bug that plagued me all these years, causing my color
management effort to fail since my first day as a Krita user -- I always use 2
monitors, and the lower one is always set to "Primary" or #1 in the system's
Display settings. I was perplexed by things like the dark areas being too
black, but since 2 monitors were both sRGB, and they had outstanding color
accuracy, I never had any clue.
Recently I replaced all my old displays. My top display is still sRGB, but the
lower one is now AdobeRGB. After calibration and profiling, the sheer amount of
over-saturation on the lower screen and the de-saturation on the top screen
naturally led me to the assumption that the sRGB display's profile was applied
to the AdobeRGB display, and vise versa. I was right, and I tested my theory on
KDE Plasma, Gnome, Windows 10. It happened everywhere.
I think this issue should be consider critical -- it breaks color accuracy in a
properly configured color managed workflow. Thanks to this bug, many of my
previous pictures are irreversibly affected in a bad way. Thank god I'm mostly
a hobbyist XD. I suggest if we can't fix the bug soon, we at least remove that
checkbox and add a warning below the screen list.
#########
Possibly related:
https://bugs.kde.org/show_bug.cgi?id=412393
https://bugs.kde.org/show_bug.cgi?id=407498
https://bugs.kde.org/show_bug.cgi?id=412608
--
You are receiving this mail because:
You are watching all bug changes.
