Bug 197353

Summary:	Colormanagement is somehow broken
Product:	[Applications] digikam	Reporter:	krienke
Component:	ColorManagement-Core	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, marcel.wiesweg
Priority:	NOR
Version First Reported In:	0.10.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	6.2.0
Sentry Crash Report:
Attachments:	color circle for testing color management

Description krienke 2009-06-21 11:38:54 UTC

Version:           0.10 (using KDE 4.2.4)
OS:                Linux
Installed from:    SuSE RPMs

I a news group I found a jpg that can be used to check if color management is allright. The jpg (see attachment farbmanagement.jpg) is a colorwheel and contains color labels (in german) inside the wheel. The trick is: The color labels inside the wheel do only appear in the correct color (their names describes) if colormanagement does work correctly. Else the label appears in a color different from its name. 

I enabled colormanagement in digikam and choose sRGB as my working space and for my display. When I open the colorframe pic in digikam, digikam wants to convert it but then colors are still wrong. Opening this jpg in gimp everything is correct. Opening it in bibble everything is correct. By the way: Both applications (gimp and digikam) do not need any setup for colormanagement. It just works.

So it seems digikams colormangement is somehow not working correctly.

For guys who are not capabale of understanding german: Here are the translations of the german color labels inside the color wheel into english:

Rot:  red
Gelb: yellow
Grün: green
Cyan: cyan
Blau: blue
Purpur: purple

Comment 1 krienke 2009-06-21 11:40:01 UTC

Created attachment 34709 [details]
color circle for testing color management

Comment 2 Marcel Wiesweg 2009-06-22 10:38:35 UTC

Yes this has been around for quite some time. Color management is seriously broken. I mark as duplicate of a report referring to a similar test image.

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

Comment 3 caulier.gilles 2019-07-28 02:04:19 UTC

Fixed with bug #182272