| Summary: | Problems with ICC profile type recognition | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Christoph Karle <ckarle> |
| Component: | ColorManagement-Profiles | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.5.0 | |
| Sentry Crash Report: | |||
|
Description
Christoph Karle
2006-04-05 20:36:45 UTC
El Mi Yes those are the files that I mean. But the problem is, that digikam ask me for a profile, when I open a .nef and then crashes with: lcms: Error #12288; Input profile is operating on wrong colorspace KCrash: Application 'digikam' crashing... and I think that's because I don't have an input profile selected. If I disable color management and use the color management plugin, I don't have a color managed view. Regards Christoph El Jueves, 6 de Abril de 2006 21:08, Christoph Karle escribi Hi Paco, i've got the same problems here NKDBase_NEF.icm ==> UNKNOW device class (1852534886) and crash if I use as input profile (nikon lab) with lcms: Error #12288; Input profile is operating on wrong colorspace KCrash: Application 'digikam' crashing... hth, Marcus. Can you give a GDB backtrace to locate where is the problem in source code ? Gilles Caulier As I said in my previous mail, the problem is dued to a color spaces conflict. I talked about this 1 or 2 months ago, but we don't reach any conclusion, so this possible bug isn't solved. About profiles with uncompletes fields, I talked about them too. As i said in one of my emails ( I don't remember which one), in previous versions of digiKam some kind of profiles (not tagged as "input device class") was included as "input" icc, like sRGB profiles, but later this was considered as a possible bug and was fixed, so only profiles tagged as "Input devices" are showed, in fact, only profiles with "device class" tag are taken in account as candidates for input, workspace, display or proof profiles. I any case, I m sure I've fixed some race conditions to avoid digiKam crashes dued to errors with lcms, as you propposed me. I'm going to review it. Paco Cruz Marcus, can you reproduce this problem again using a fresh svn checkout ? Thanks in advance Gilles Caulier It does not crash anymore if I use the Nikon Lab as Colorspace for the Input. But NKDBase_NEF.icm is still not known (==> UNKNOW device class (1852534886)) hth, Marcus. yes, the lcms crash handler have been enabled everywhere. About icc file recognition, the error is reported by lcms, not digiKam directly. Perhaps this problem will be fixed in future release of lcms. Gilles I think it's time to close this bug, since it depends on Little CMS stuff. I don't know if WONTFIX is the right tag. Feel free to correct it. Paco Cruz |