Bug 237494 - B&W JPEG displayed incorrectly
Summary: B&W JPEG displayed incorrectly
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Preview-Image (show other bugs)
Version: 1.1.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-13 13:41 UTC by francois
Modified: 2018-09-02 08:47 UTC (History)
1 user (show)

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

Attachments
KDE B&W JPEG displayed incorrectly, in spite of thumbnail being correct (53.96 KB, image/jpeg)
2010-05-13 13:43 UTC, francois 		Details
Offending image for testing purposes (more where this came from) (418.41 KB, image/jpeg)
2010-05-13 13:44 UTC, francois 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description francois 2010-05-13 13:41:33 UTC 
Version:           1.1.0 (using KDE 4.4.0)
Compiler:          MSVC 32bit 
OS:                MS Windows
Installed from:    MS Windows

B&W JPEGs are displayed with a strange interlacing pattern. This fault is common to DigiKam and ShowFoto. Gimp doesn't have the problem. However, the thumbnail is displayed correctly.

Screen dump attachement to follow.
Comment 1 francois 2010-05-13 13:43:16 UTC 
Created attachment 43533 [details]
KDE B&W JPEG displayed incorrectly, in spite of thumbnail being correct
Comment 2 francois 2010-05-13 13:44:09 UTC 
Created attachment 43534 [details]
Offending image for testing purposes (more where this came from)
Comment 3 caulier.gilles 2010-05-13 18:36:04 UTC 
Do you use color management ?

Look this entry : https://bugs.kde.org/show_bug.cgi?id=237492

Gilles Caulier
Comment 4 francois 2010-05-13 23:36:55 UTC 
Thanks for this. Indeed the problem images are color-managed. If the profile is removed, they are displayed correctly.

This is a duplicate bug.
Comment 5 caulier.gilles 2010-05-14 07:47:53 UTC 

*** This bug has been marked as a duplicate of bug 237492 ***
Comment 6 caulier.gilles 2018-09-02 08:47:33 UTC 
Not reproducible with 6.0.0