Cannot import tiff with deflate compression

Bug #602824 reported by Ross Gardiner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Triaged
Low
Unassigned
Inkscape Devlibs
Triaged
Undecided
Unassigned

Bug Description

When trying to import a deflate-compressed tiff into Inkscape 0.48 prerelease, after selecting whether to link or embed, I get a message saying that Inkscape 'failed to load the requested file'. I believe, although I am not sure, that these files worked in previous versions. LZW-compressed tiffs still work fine.

Platform:
Inkscape 0.48pre1 r9509
Windows XP MCE 32-bit

Revision history for this message
su_v (suv-lp) wrote :

Can you attach a sample TIFF file that fails to import?

tags: added: bitmap importing
Revision history for this message
Ross Gardiner (ross-gmx) wrote :

Saved as TIFF with Deflate compression in the GIMP 2.6.8

Revision history for this message
su_v (suv-lp) wrote :

not reproduced with Inkscape 0.47 and 0.47+devel r9587 on OS X 10.5.8

- In both Inkscape versions the TIFF file imports without errors.
- GIMP on OS X 2.6.8 also opens the file without problems.
- Apple's default image viewer (Preview.app, Version 4.2 (469.5)) however fails with the error message "Couldn’t open the file. It may be corrupt or a file format that Preview doesn’t recognize."

Revision history for this message
su_v (suv-lp) wrote :

@JazzyNico - can you test on linux? Possibly a problem affecting 'inkscape-devlibs' for the win32 port?

Revision history for this message
jazzynico (jazzynico) wrote :

I've reproduced this bug ('failed to load the requested file') the first time I've imported (embedded) the file on Ubuntu, Inkscape r9582, but now I can't reproduce it, even after restarting Inkscape!
I'll try again on Windows XP tomorrow.

Revision history for this message
su_v (suv-lp) wrote :

When embedding the TIFF file (r9587), and realigning it after changing the page size, I get the same console warnings as in bug #597689:

** (inkscape-bin:61531): WARNING **: GC Warning: Repeated allocation of very large block (appr. size 15503360):
 May lead to memory leak and poor performance.

** (inkscape-bin:61531): WARNING **: GC Warning: Repeated allocation of very large block (appr. size 15503360):
 May lead to memory leak and poor performance.

Revision history for this message
jazzynico (jazzynico) wrote :

Confirmed on Windows XP, Inkscape 9535, but not reproduced with 0.47.

I still can't reproduce it on Ubuntu. I guess the file was not completely downloaded when I first tried to import it.

Changed in inkscape:
importance: Undecided → Low
status: New → Confirmed
tags: added: win32
Revision history for this message
jazzynico (jazzynico) wrote :

Reproduced again on Windows XP, Inkscape trunk revision 13279, official devlibs.
Not reproduced with the experimental GTK3 devlibs, same OS and Inkscape version.

Changed in inkscape-devlibs:
status: New → Triaged
Changed in inkscape:
status: Confirmed → Triaged
Revision history for this message
Alvin Penner (apenner) wrote :

on Windows XP, Inkscape trunk revision 13245, official devlibs, I get the console messages.

(inkscape.exe:3984): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Couldn't load bitmap
GdkPixbuf loader failed

Revision history for this message
jazzynico (jazzynico) wrote :

New tests with recent libtiff libraries (tested with 3.9.7 and 4.0.6) still don't work on Windows XP (32bit). Very likely a GdkPixbuf loader issue...

Revision history for this message
jazzynico (jazzynico) wrote :

And probably a duplicate of (or strongly related to) Bug #1153777 "Import cmyk-tiff crashes".

Revision history for this message
jazzynico (jazzynico) wrote :

Bad new, we already have the most recent gdk-pixbuf version that is compatible with our glib package, and thus there's nothing we can do for now except recompiling almost the whole devlibs.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.