Bug 200153 - digikam color profile error
Summary: digikam color profile error
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ColorManagement-Profiles (show other bugs)
Version: 0.10.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-14 11:14 UTC by Peter Kloth-Schad
Modified: 2022-02-01 11:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.2.0
Sentry Crash Report:


Attachments
Example (341.16 KB, image/jpeg)
2009-07-15 07:03 UTC, Peter Kloth-Schad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Kloth-Schad 2009-07-14 11:14:52 UTC
Version:           0.10.0 (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-13-generic

By loading and at least saving a photo with embedded sRGB ICC-profile (out of the Sony-R1 or Panasonic TZ5) seems the original sRGB-profile overwritten with a mismatching profile. The result is, when this photo then will be opened with gimp or a browser like firefox 3.0.1 (with color management switched on) then comes the picture with a heavy blue tint. A neutral grey photo comes blue.
That occurs always, even when i load and save the photo without any manipulation at the picture. 
Switching in or off the digikam color management ist without any effect for this and that was so also in the recent versions.
All plugins are loaded.
Greetings
Peter
Comment 1 Peter Kloth-Schad 2009-07-15 07:03:23 UTC
Created attachment 35342 [details]
Example

A photo, taken with Panasonic Lumix TZ5.
The file coms with an sRGB-buildt-in ICC-profile.
I load the file to digicam and save after manipulating size and color etc.
The color should be neutral grey and it looks blue tinted, when opened with firefox 3.. by color management 'on'
Comment 2 Greg Kennedy 2009-08-04 22:30:58 UTC
Duplicate of https://bugs.kde.org/show_bug.cgi?id=165650
Comment 3 caulier.gilles 2009-08-15 11:09:56 UTC

*** This bug has been marked as a duplicate of bug 165650 ***
Comment 4 caulier.gilles 2019-07-28 02:05:42 UTC
Fixed with bug #165650