Bug 242833 - Compressed TIFF from digikam broken
Summary: Compressed TIFF from digikam broken
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-DImg-TIFF (show other bugs)
Version: 1.3.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-26 02:51 UTC by Michal Thoma
Modified: 2017-07-30 16:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.2.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Thoma 2010-06-26 02:51:32 UTC 
Version:           1.3.0 (using KDE 4.4.4) 
OS:                Linux

The compressed TIFF output from digikam editor or batch processor is broken. The created image displays with totally wrong colors and emboss-like shapes. Everything was allright with digikam 1.2.0. Surprisingly image thumbnail is displayed correctly while image view is totally wrong in digikam and other applications too.

The libTiff version used is 3.9.2

Reproducible: Always

Steps to Reproduce:
Open image in editor, do "save as", select tiff and check compression. Save image and the view image in digikam or elsewhere.

Actual Results:  
The image displayed is totally mismatched.  

Expected Results:  
The image will be displayed correctly.
Comment 1 Manuel Viet 2010-07-03 14:45:44 UTC 
I confirm this bug, same symptoms here, libtiff 3.8.2.

Best guesswork : endianness issue.
Comment 2 Olleg Samoylov 2010-10-21 01:09:16 UTC 
Images are Looked like in bug:
https://bugs.kde.org/show_bug.cgi?id=211758
Still exist in 1.5.0 and the svn trunk.
Comment 3 Marcel Wiesweg 2011-01-24 16:10:03 UTC 
I have just now successfully created a compressed TIFF with 2.0 from SVN (note: 2.0-beta1 will have a bug saving the file as JPEG), as confirmed by tiffinfo, which can be opened by gwenview and the gimp.

Any special considerations here? Maybe the bug is simply solved, or it needs special input.
Comment 4 Michal Thoma 2011-01-30 19:05:40 UTC 
I can only say, that it's not fixed in 1.8.0...
Comment 5 Marcel Wiesweg 2011-09-24 13:31:48 UTC 
Feel free to reopen if still present in 2.2