Bug 347157

Summary:	Color management with rendering intent and custom monitor profile support
Product:	[Applications] gwenview	Reporter:	DrSlony <bugs>
Component:	general	Assignee:	Gwenview Bugs <gwenview-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	bugs, jkt, myriam
Priority:	NOR
Version First Reported In:	5.0.0
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description DrSlony 2015-05-04 12:53:28 UTC

Greetings

Thank you and well done porting Gwenview to frameworks/plasma 5. One very important feature missing is color management within gwenview. Please add support for it, specifically to allow one to use a custom monitor profile (regardless of the installed system monitor profile), to allow one to select an image profile (embedded/custom/disable color management) and also allow the user to change the rendering intent - extremely important when viewing not only wide-gamut images but even sRGB images (most home monitors don't even cover sRGB's gamut!).

Reproducible: Always

Comment 1 Jan Kundrát 2015-05-28 21:30:50 UTC

I think that this is a "patches are welcome" thing.

Just FYI, the actual color management *is* there, but it was being ignored since v4.9.80 (commit 5f888618) unless the image happened to have a recognized ICC profile. I hope that this is fixed by https://git.reviewboard.kde.org/r/123928/ . With this patch, at least the display profile which is e.g. set by colord is respected.

Comment 2 DrSlony 2016-12-19 20:32:48 UTC

Hello again. How do I make Gwenview use my monitor color profile, and what is the status of color management in Gwenview since the last comment, has anything changed?

Comment 3 DrSlony 2016-12-19 21:31:50 UTC

I see that Gwenview is using my monitor color profile thanks to Argyll's dispwin, but it is still using the perceptual rendering intent instead of relative colorimetric, which is bug 359909
https://bugs.kde.org/show_bug.cgi?id=359909

Comment 4 Jan Kundrát 2016-12-20 09:53:16 UTC

...which means that this bug can be closed. Yes, gwenview uses your systemwide monitor profile which can be set by a plethora of tools (colord-kde, argyll, etc).

Comment 5 DrSlony 2016-12-20 15:38:42 UTC

I would not consider this issue to be closable as Gwenview lacks the basic settings described in the first comment.

"can be set by a plethora of tools (colord-kde, argyll, etc)."
colord-kde didn't work with Plasma last time I tried it, Argyll's dispwin simply sets the X11 atom, Oyranos didn't work with Plasma last time I tried it, kolor-manager is dead last time I checked, I don't recall any others...

Comment 6 Jan Kundrát 2016-12-20 17:21:23 UTC

(In reply to DrSlony from comment #5)
> I would not consider this issue to be closable as Gwenview lacks the basic
> settings described in the first comment.

I believe that this bug is effectively a duplicate of these two:

- rendering intent: #359909
- custom monitor profiles: #360075

> colord-kde didn't work with Plasma last time I tried it, Argyll's dispwin
> simply sets the X11 atom, Oyranos didn't work with Plasma last time I tried
> it, kolor-manager is dead last time I checked, I don't recall any others...

FYI, I've been using colord-kde with Plasma 5 for several years. I'm seeing some issues with auto-applying a monitor profile during hotplug events and docking/undocking which sometimes require a restart of the KDE's color daemon service. That's off-topic here, though.