Summary: | Page is rendered almost completely blank | ||
---|---|---|---|
Product: | jbig2dec | Reporter: | Marcos H. Woehrmann <marcos.woehrmann> |
Component: | Rendering | Assignee: | Ralph Giles <ralph.giles> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | CC: | mlungu777 |
Priority: | P2 | ||
Version: | master | ||
Hardware: | All | ||
OS: | All | ||
Customer: | 580 | Word Size: | --- |
Description
Marcos H. Woehrmann
2008-05-19 00:09:18 UTC
Created attachment 4030 [details]
img-Z28145827-0001.pdf
Testing with the luratech build of Ghostscript shows some warnings which imply that it's a JBIG2 issue: GPL Ghostscript 8.62 (2008-02-29) Copyright (C) 2008 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 2. Page 1 Luratech JBIG2 ERROR 0xffffffff as segment data length is not currently supported! **** Warning: File has insufficient data for an image. Luratech JBIG2 ERROR 0xffffffff as segment data length is not currently supported! **** Warning: File has insufficient data for an image. Page 2 Luratech JBIG2 ERROR 0xffffffff as segment data length is not currently supported! **** Warning: File has insufficient data for an image. Luratech JBIG2 ERROR 0xffffffff as segment data length is not currently supported! **** Warning: File has insufficient data for an image. Luratech JBIG2 ERROR 0xffffffff as segment data length is not currently supported! **** Warning: File has insufficient data for an image. **** This file had errors that were repaired or ignored. **** The file was produced by: **** >>>> Xerox WorkCentre 7345 <<<< **** Please notify the author of the software that produced this **** file that it does not conform to Adobe's published PDF **** specification. Yes, this is the same issue as bug 689841, and the is from a different model of Xerox WorkCenter. jbig2dec should be reporting a similar error, but instead fails silently. The patch committed as r8778 allows Ghostscript to decode this file. *** Bug 689841 has been marked as a duplicate of this bug. *** |