[Digikam-devel] [digikam] [Bug 322789] Enabling "color managed view" in editor slows down tool startup

Peter Albrecht px79 at crazymonkeys.de
Fri Jul 26 16:08:30 BST 2013


--- Comment #3 from Peter Albrecht <px79 at crazymonkeys.de> ---
I guess my digiKam is using lcms 2.3 (version 2030):

digiKam version 3.2.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibEigen: 3.0.6
LibExiv2: 0.23
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.10.4
LibKExiv2: 2.3.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.2.0
LibLCMS: 2030
LibPGF: 6.12.27 - external shared library
LibPNG: 1.5.15
LibQt: 4.8.4
LibRaw: 0.15.0-Beta1
LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.15.1 (stable version)
Parallelized PGF codec: No
Parallelized demosaicing: No
RawSpeed codec support: No
Database backend: QSQLITE
Kipi-Plugins: 3.2.0
LibKface: 2.0.0
LibKipi: 2.0.0
LibOpenCV: 2.4.5
Libface: 0.2

But there is also a lcms 1.19 installed on my  computer.

Is it a problem, that the different lcms-versions a used by different digikam
  media-gfx/digikam-3.2.0 (media-libs/lcms:2)
  kde-base/libkdcraw-4.10.4 (media-libs/lcms:0)
  kde-base/libkexiv2-4.10.4 (media-libs/lcms:0)
Slot 0 means lcms 1.19, slot 2 means lcms 2.3

You are receiving this mail because:
You are the assignee for the bug.

More information about the Digikam-devel mailing list