Version: 0.10.0 from svn (using KDE 4.2.1) OS: Linux Installed from: Compiled From Sources I've used the svn versions for some time now. Yesterday I compiled the latest version and discovered that assigning a color profile does not work anymore. Use case: - My workspace profile is set to AdobeRGB - I load a TIF16 image with an embedded "Nikon Adobe RGB" profile into the editor - the editor asks me whether I want to convert, assign or do nothing - I choose assign as the profiles are identical and to avoid the message showing up again in future - when I save this image the profile is still the "Nikon Adobe RGB" The last version from svn (compiled approx. end of February) which I was using until yesterday worked as expected.
Just re-checked with rev. 945637 from svn: Assigning color profiles is working again! Thanks Gilles for your fast support. Günther
Hi, This bug showed up again. Same behaviour like described in the original post. TIA, Guenther
And you use current code from svn trunk ? Gilles caulier
(In reply to comment #3) > And you use current code from svn trunk ? > Hi Gilles, Sorry forgot to mention it: Yes, Version 1.0.0-beta6 (rev.: 1038724) checked out and compiled yesterday. Guenther
Ok. strange, because Marcel has rewritten all ICC color management code in digiKam When you said that it still Adobe Rgb, where you see this information ? In image metadata ? In ICC panel from right side bar ? In image properties ? Gilles Caulier
Now that the dialog has been rewritten the original bug strictly cannot show up anymore ;-) So some additional questions: which options did you choose in the color management dialog? Can you provide a sample picture (private mail would be ok)
Maybe it could even be that you still use the old plugin? :-) When you have not deinstalled digiKam SVN in the past, chances are that both plugins are installed? At least this can happen sometimes with kipiplugins...
(In reply to comment #7) > Maybe it could even be that you still use the old plugin? :-) > When you have not deinstalled digiKam SVN in the past, chances are that both > plugins are installed? At least this can happen sometimes with kipiplugins... It works again - so it must be something like that... What I have done now to eliminate dependencies: - upgraded from kde 4.2.4 to 4.3.2 - upgraded qt from 4.4.3 to 4.5.2 - de-installed all svn digikam and kipi-plugins installations - checked out and compiled everything again Sorry for bothering you! Guenther