| Summary: | DigiKam complains about invalid ICC profiles path | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Dik Takken <kde> |
| Component: | Setup-ColorManagement | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 0.9.0 | |
| Sentry Crash Report: | |||
| Attachments: | digikamrc | ||
|
Description
Dik Takken
2006-08-06 12:01:42 UTC
In Beta2, I still get this message on every image I open in the editor. Is there any progress on color management in Digikam? It is still completely broken in 0.9.0-Beta3... It works perfectly in CinePaint though. Paco, can you check this report. Thanks in advance Gilles Dik, what is your icc repository path ? In local or remote place ? What right is set to this path ? Gilles My icc profile path is: ~/.color/icc both '.color' and '.color/icc' have access rights 'drwxr-xr-x'. I tried moving the icc directory to my desktop and point DigiKam to that directory, but I keep getting the same error message. Are you some error messages in the console ? Nota : i cannot reproduce this problem here (:=)))... Can you attach your "~/.kde/share/config/digikamrc" setup file please ? Thanks in advance Gilles Created attachment 18737 [details]
digikamrc
here it is.. Opening an image in the image editor generates the following messages on console: kdeui (KDatePicker): KDatePicker::dateChangedSlot: date changed (2006/11/30). kio (KTrader): query for Digikam/ImagePlugin : returning 30 offers QFile::open: No file name specified digikam: Exif Orientation: 1 After clicking OK on the error message, a get a few dozen of these on the terminal: digikam: intent: 0 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 sorry about flooding your mail boxes.... :) no problem. My mail box is full of messages for digiKam world (:=)))... Give me an attachement with all your icc profiles used to import a picture in editor (camera and workspace) Gilles ok, this is the problem : [Color Management] BPCAlgorithm=false BehaviourICC=false CMInRawLoading=false DefaultPath=$HOME/Desktop/icc EnableCM=true InProfile=0 InProfileFile= ==> there is no ICC file set like Input profile ! ManagedView=true MonitorProfile=4 MonitorProfileFile=$HOME/Desktop/icc/Monitor Gamma 2.2.icc ProofProfile=11 ProofProfileFile=$HOME/Desktop/icc/fsnEnduraSupraGlossyV2.icc RenderingIntent=0 WorkProfileFile=/usr/share/apps/digikam/profiles/srgb.icm WorkSpaceProfile=7 Normally it's impossible to use CM without an input ICC profile. Just to test, set one input ICC profile on the list an try again. Gilles Ok, i can reproduce the problem here... now... I will fix it. Gilles I don't have an input profile for my camera, or any other input profile for testing. So I had to leave it blank. Thanks for looking into the problem! Are you working with JPEG or RAW files ? Witch bits color depth you use to decode RAW files ? 8 or 16 ? Gilles I work with 8-bit JPEG images (cheap digital camera) and 16-bit TIFF (slide scanner) As a side note: I was already wondering what DigiKam was doing to files that do not have an embedded profile. CinePaint will ask which profile to assign to the image, if no default has been set. I was thinking that the 'input profile' was for importing from digital camera's only, not for existing images on harddisk. Dik, Please checkout svn and give me a feedback. I have fixed a lot of problems in Color Management with commit #609570. Look svn log for details or digikam-devel ML where this commit is CC. Gilles This bug have been fixed in current svn implementation. I close this file now. Gilles |