After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674190 - Cannot open tiff files
Cannot open tiff files
Status: RESOLVED DUPLICATE of bug 673729
Product: GIMP
Classification: Other
Component: Plugins
2.8.0-RC1
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-04-16 10:33 UTC by JAMA
Modified: 2012-04-16 11:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Error message (CS localization) (76.07 KB, image/jpeg)
2012-04-16 10:33 UTC, JAMA
Details

Description JAMA 2012-04-16 10:33:52 UTC
Created attachment 212129 [details]
Error message (CS localization)

The windows installation does not open tiff files.
Tiff plugin: Cannot read TIFF header
For error message, see attached image

Procedure
I installed new version of 2.8.0-RC1, the previous version 2.6.x... opened the same file without problems. 
Note I am using 64bit version of Win7 and used installer from http://www.gimpusers.com/downloads/8-gimp-2-7-1-windows-32-64-bit 
(I am not sure if it automatically determined version 32/64bit to install, so cannot say what version is installed on my PC)

Some related discussion on the issoue are to be found on 
http://gimper.net/viewtopic.php?f=53&p=112723
Comment 1 Michael Schumacher 2012-04-16 10:56:38 UTC
Duplicate of bug #673729?
Comment 2 JAMA 2012-04-16 11:12:38 UTC
Yes it is duplicate.
I replace libtiff-5.dll for libtif-3.dll from older installation and it works. It means it is the same bug.

I also reproduced this bug with productin 2.6.12 and development 2.7.5. The installation is removed from my PC so I cannot check, but I guess the same libtiff-5.dll library with bug was used there.
Comment 3 André Klapper 2012-04-16 11:27:41 UTC

*** This bug has been marked as a duplicate of bug 673729 ***