Hello Gwenview 15.12.1 uses the _X11_PROFILE atom if its set, which is nice because that way the image shown is color-corrected for the loaded monitor profile, but there is no way in Gwenview to control the color management. Please add: 1- A possibility to toggle color management on/off. Just because one has the _X11_PROFILE set doesn't mean one needs to use it. 2- A possibility to select a different monitor profile. A very common misconception is that there is such a thing as "one correct profile", but that is not true. A monitor profile serves a purpose - you could have one for working on typical photos, one for working on photos with extreme colors where they must not be clipped, one for matching prints, etc. Reproducible: Always
I am using openSUSE Leap 42.1 and the latest gwenview from the official repo (in Help > About I get 4.14.0 pre) All the images I open are with wrong colors. I have a wide gamut calibrated EIZO CG. I have installed: kolor-manager (with oyranos) kdebase4-workspace-addons In systemsettings I have correctly configured my both monitors and in Firefox all colors are fine (tested aRGB and sRGB images). In RawTherapee also everything checks. Today I also installed: colord colord-kde gnome-color-manager And chose the correct color profile for the monitor in colord-kde, installed it system wide. No change whatsoever - the colors are still wrong (oversaturated as when color profiles are stripped/ignored). It seems impossible to make gwenview display colors correctly.
Additional info: I am using Plasma desktop which comes with Leap.
(In reply to DrSlony from comment #0) > 1- A possibility to toggle color management on/off. Just because one has the > _X11_PROFILE set doesn't mean one needs to use it. I disagree. To my understanding, this is what that atom is for. Why do you set it when you do not plan to use it? > 2- A possibility to select a different monitor profile. A very common > misconception is that there is such a thing as "one correct profile", but > that is not true. A monitor profile serves a purpose - you could have one > for working on typical photos, one for working on photos with extreme colors > where they must not be clipped, one for matching prints, etc. Understood -- but perhaps you might want to use a tool which supports soft-proofing when you want to soft-proof rather than changing your screen's color profile. (In reply to george from comment #1) > I am using openSUSE Leap 42.1 and the latest gwenview from the official repo > (in Help > About I get 4.14.0 pre) That's two years old now.
Why do you insist on closing issues when you have demonstrated a lack of understanding of color management? Random example for point 1: because you want to match what you see in Gwenview to what you see in your non-colormanaged web browser. Point 2 is only partially related to soft-proofing. Your "TL;DR" attitude in the other issue has really put me off.
I have just found that I was using the wrong repo. After updating to 15.12.3 I can see correct colors. Thanks Jan.
> Random example for point 1: because you want to match what you see in > Gwenview to what you see in your non-colormanaged web browser. I do not consider a checkbox "ignore system settings and reproduce buggy behavior of a non-color-managed web browser" to be a reasonable use case for a basic image viewer. Yes, I can think of use cases where this might be handy. As you say, one might want to check what a different user with a different wide-gamut screen will see in their non-color managed web browser. I might also want to check how my printed pictures will look like. These are good use cases in general, but I don't think that they are good use cases for Gwenview given the available manpower. Feel free to disagree and reopen this bug; maybe someone will tackle it.