Version: (using KDE KDE 3.5.6) Installed from: Ubuntu Packages OS: Linux I recently moved to Feisty Fawn . Previously i was on Dapper (Ubuntu). Since i have moved to Festy i have a problem with the icc color profiles management that seems not working well anymore. Ex: - i define a workspace color profile in the configuration dialog : ex Adobe RGB or Apple RGB - my photos have an embedded profile 'sRGB' - when i open the photo editor , a dialog box asks me either to convert , to assign , to skip ... - i ask to convert the profile but no change in the colors rendering and i get the following messages (if i start digikam in a term window) lcms: Error #4096; Read from memory error. Got 0 bytes, block should be of 128 bytes lcms: Error #12288; Corrupted memory profile I am quite sure of the profile files : - no change in the profile files for a while - same default when playing with the profiles provided with digikam - krita works using the same profile files - if i define Adobe RGB or Apple RGB as a profile for the display and sRGB for the workspace the color rendering works So it seems a bug when entering the editor The version i am using is the latest 0.9.2 here are the lines in source.list file ## digikam deb http://www.mpe.mpg.de/~ach/kubuntu/feisty ./ deb-src http://www.mpe.mpg.de/~ach/kubuntu/feisty ./
SVN commit 723326 by cgilles: digiKam from trunk (KDE4) : ICC color profile settings page : important bugfix here : never use the QComboBox::currentText() with SQueezedComboBox, else the icc profile name can be truncated and unsuitable for color management. Always use SQueezedComboBox::itemHighlighted() instead. CCBUGS: 148151 M +12 -12 setupicc.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=723326
SVN commit 723334 by cgilles: backport commits #723326 on digiKam for KDE3 CCBUGS: 148151 M +8 -8 setupicc.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=723334
jpv, I think than i have found the problem in current implementation. I have patched KDE3 svn source code. The fix will be integrated into next 0.9.3-beta2 (0.9.3-beta1 release do not include it). I would to have your feedback. Can you test using current svn implementation ? Gilles Caulier
Gilles, Sorry but I am using the Ubuntu depot from Achim (Feisty Fawn) and i dont have svn and the compilation toolkit installed. So i am afraid that it can be painfull for me to build digikam from source. If they is a mean to provide me with a Digikam Feisty Fawn compatible binary. I will be happy to test it. Thank for you help Regards jpv Le mardi 09 octobre 2007 à 11:11 +0000, Gilles Caulier a écrit : [bugs.kde.org quoted mail] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.14.1"> </HEAD> <BODY> Gilles,<BR> <BR> Sorry but I am using the Ubuntu depot from Achim (Feisty Fawn) and i dont have svn and the compilation toolkit installed.<BR> So i am afraid that it can be painfull for me to build digikam from source.<BR> If they is a mean to provide me with a Digikam Feisty Fawn compatible binary. I will be happy to test it. <BR> Thank for you help <BR> Regards<BR> jpv <BR> <BR> <BR> <BR> <BR> <BR> Le mardi 09 octobre 2007 à 11:11 +0000, Gilles Caulier a écrit : <BLOCKQUOTE TYPE=CITE> <PRE> <FONT COLOR="#000000">------- You are receiving this mail because: -------</FONT> <FONT COLOR="#000000">You reported the bug, or are watching the reporter.</FONT> <FONT COLOR="#000000"> </FONT> <FONT COLOR="#000000"><A HREF="http://bugs.kde.org/show_bug.cgi?id=148151">http://bugs.kde.org/show_bug.cgi?id=148151</A> </FONT> <FONT COLOR="#000000">------- Additional Comments From caulier.gilles gmail com 2007-10-09 13:11 -------</FONT> <FONT COLOR="#000000">jpv,</FONT> <FONT COLOR="#000000">I think than i have found the problem in current implementation.</FONT> <FONT COLOR="#000000">I have patched KDE3 svn source code. The fix will be integrated into next 0.9.3-beta2 (0.9.3-beta1 release do not include it).</FONT> <FONT COLOR="#000000">I would to have your feedback. Can you test using current svn implementation ?</FONT> <FONT COLOR="#000000">Gilles Caulier</FONT> </PRE> </BLOCKQUOTE> </BODY> </HTML>
Achim, Any way to help jpv ? Gilles
Hi Gilles I have finally downloaded and i have compiled digikam 0.93 final from the source , i was looking forward the new features of the new version ... Thank again for developing Digikam and my best wishes for 2008 Concerning the bug , it seems partly solved with 0.93 let me give some details : 1) The color conversion works if the picture has no embedded profile : if the picture comes without any embedded profile the color conversion applies 2) if the picture has an embedded profile the problem remains the same "digikam: Found JPEGLossless plugin digikam: /Documents_linux/brouillons/Photos/Vacances Ete/2002 Agde (aout)/10000012.jpg : JPEG file identified digikam: Found JPEGLossless plugin digikam: /Documents_linux/brouillons/Photos/Vacances Ete/2005_Savoie/pict0009.jpg : JPEG file identified digikam: Exif color-space tag is sRGB. Using default sRGB ICC profile. digikam: Embedded profile: sRGB lcms: Error #4096; Read from memory error. Got 0 bytes, block should be of 128 bytes lcms: Error #12288; Corrupted memory profile digikam: Error: Input profile is NULL " 3) if i define a profile for the monitor it doesnt work Thank for your help JP Le mardi 09 octobre 2007 à 20:06 +0000, Gilles Caulier a écrit : [bugs.kde.org quoted mail] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.14.1"> </HEAD> <BODY> Hi Gilles <BR> <BR> I have finally downloaded and i have compiled digikam 0.93 final from the source , i was looking forward the new features of the new version ... Thank again for developing Digikam and my best wishes for 2008 <BR> <BR> Concerning the bug , it seems partly solved with 0.93 <BR> <BR> let me give some details :<BR> <BR> 1) The color conversion works if the picture has no embedded profile : if the picture comes without any embedded profile the color conversion applies <BR> <BR> <BR> 2) if the picture has an embedded profile the problem remains the same <BR> <BR> "digikam: Found JPEGLossless plugin<BR> digikam: /Documents_linux/brouillons/Photos/Vacances Ete/2002 Agde (aout)/10000012.jpg : JPEG file identified<BR> digikam: Found JPEGLossless plugin<BR> digikam: /Documents_linux/brouillons/Photos/Vacances Ete/2005_Savoie/pict0009.jpg : JPEG file identified<BR> digikam: Exif color-space tag is sRGB. Using default sRGB ICC profile.<BR> digikam: Embedded profile: sRGB<BR> lcms: Error #4096; Read from memory error. Got 0 bytes, block should be of 128 bytes<BR> lcms: Error #12288; Corrupted memory profile<BR> digikam: Error: Input profile is NULL<BR> "<BR> <BR> <BR> 3) if i define a profile for the monitor it doesnt work <BR> <BR> <BR> Thank for your help<BR> JP <BR> <BR> <BR> <BR> Le mardi 09 octobre 2007 à 20:06 +0000, Gilles Caulier a écrit : <BLOCKQUOTE TYPE=CITE> <PRE> <FONT COLOR="#000000">------- You are receiving this mail because: -------</FONT> <FONT COLOR="#000000">You reported the bug, or are watching the reporter.</FONT> <FONT COLOR="#000000"> </FONT> <FONT COLOR="#000000"><A HREF="http://bugs.kde.org/show_bug.cgi?id=148151">http://bugs.kde.org/show_bug.cgi?id=148151</A> </FONT> <FONT COLOR="#000000">caulier.gilles gmail com changed:</FONT> <FONT COLOR="#000000"> What |Removed |Added</FONT> <FONT COLOR="#000000">----------------------------------------------------------------------------</FONT> <FONT COLOR="#000000"> CC| |ach mpe mpg de</FONT> <FONT COLOR="#000000">------- Additional Comments From caulier.gilles gmail com 2007-10-09 22:06 -------</FONT> <FONT COLOR="#000000">Achim, </FONT> <FONT COLOR="#000000">Any way to help jpv ?</FONT> <FONT COLOR="#000000">Gilles</FONT> </PRE> </BLOCKQUOTE> </BODY> </HTML>
Code has been rewritten in large parts. This report is very old. I dont find a testcase in this bug report. (Please also note that converting to workspace profile does _not_ change the appearance, but the image data). Feel free to reopen if you encounter your problem with 1.0-beta4 or later.