GNOME Bugzilla – Bug 355590
Printing TIFF images I only get completely black pages
Last modified: 2007-03-22 11:24:50 UTC
Hello! Albeit being displayed correctly (even in the printing preview), trying to print TIFF images with eog I only get completely black pages. I reproduced this five times. $ file FILE.tif FILE.tif: TIFF image data, little-endian The printer is a HP LaserJet 4L, driven by CUPS, locally connected on the parallel port. Printing the files via GIMP works without problems. Also, having eog not print the files, but instead generate a pdf file works. (I didn't try printing the pdf file, though.) I could --- non-publically --- provide a copy of such a TIFF file. The system is an up-to-date Ubuntu dapper one, which means Ubuntu version 2.14.3-0ubuntu1 of eog. I realize that this might be hard to track down, but perhaps someone has an idea?
Hi there, I have the same problem with TIFF files. When I print it from gqview or evince the same file it works fine. $ file file.tiff file.tiff: TIFF image data, little-endian My system is a debian etch, I can reproduce with all my tiff files and with several printers (HP, Brother) Does anyone have an idea ?
Same here with GIF files on a machine running both Debian unstable (Eye of Gnome 2.16) and Ubuntu Dapper (eog 2.14). The printer is an HP DeskJet 950.
I can confirm the same bug. This with a Kyocera Mita MK-1650, both with Generic Postscript and proper PPD. as well as with a Konica 7033. Nothing but BLACK square the same size of the image. Can see and edit the image on the screen however. Ubuntu Dapper Hope this gets fixed quick, as I really need to print out these images !
Could you test what happens if you print TIFF images with HEAD right now? I commited a patch to use GtkPrint + cairo instead of the old libgnomeprint library.
I assume this bug is fixed in HEAD and eog-ng branches, as I already tried printing several TIFF images. If I am wrong, please feel free to reopen. So, this is fixed in current development version. The fix will be available in the next major release. Thanks for reporting this bug!
*** Bug 421395 has been marked as a duplicate of this bug. ***