Bug 13955 - pdftops generated postscript file makes printers crash!
Summary: pdftops generated postscript file makes printers crash!
Status: RESOLVED MOVED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All All
: medium major
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-07 05:51 UTC by Markus Duft
Modified: 2018-08-21 10:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Sample Input File from which broken output can be generated (13.44 KB, application/octet-stream)
2008-01-07 05:53 UTC, Markus Duft
Details
Sample Output which makes printer crash (115.55 KB, application/postscript)
2008-01-07 05:53 UTC, Markus Duft
Details
Patch for Fontconfig to build poppler on Windows with parity (2.04 KB, patch)
2008-01-07 05:54 UTC, Markus Duft
Details | Splinter Review
Patch to be able to build poppler on Windows with parity (22.53 KB, patch)
2008-01-07 05:54 UTC, Markus Duft
Details | Splinter Review

Description Markus Duft 2008-01-07 05:51:36 UTC
We have a lot of CrystalClear generated PDF files we deal with. Those PDFs containe Barcodes and such. We need them as PDF to archive those reports, but printing doesn't allways work with pdf on windows. This is why i ported poppler to compile on windows with parity (http://www.sf.net/projects/parity, i will attach a patch here). The plan was to use pdftops to create postscripts with every printer should be able to handle (am i wrong here? i'm talking about reasonably new printers ...)

Now the problem is, that with some HP printers like the HP LaserJet P3005x, the resulting PS file makes the printer crash with "Error 49.4c02". I looked it up and it says "Formatter Board Error, please update your Firmware". Ok, so i updated to the latest Firmware, but this didn't change anything.

i now played around a little and noticed that i can print the document as PS if
 * i generate PS directly with crystalclear (not an option)
 * use ghostscript to generate the PS (which i don't like)

it seems that poppler (and xpdf too for that one...) does something, others don't do... Any help would be great.
Comment 1 Markus Duft 2008-01-07 05:53:03 UTC
Created attachment 13568 [details]
Sample Input File from which broken output can be generated
Comment 2 Markus Duft 2008-01-07 05:53:30 UTC
Created attachment 13569 [details]
Sample Output which makes printer crash
Comment 3 Markus Duft 2008-01-07 05:54:13 UTC
Created attachment 13570 [details] [review]
Patch for Fontconfig to build poppler on Windows with parity
Comment 4 Markus Duft 2008-01-07 05:54:37 UTC
Created attachment 13571 [details] [review]
Patch to be able to build poppler on Windows with parity
Comment 5 Juliusz Chroboczek 2008-05-02 09:57:04 UTC
I've noticed this too.  Something is wrong with the way pdftops embeds bitmaps
in PostScript, it causes printers to run out of memory.  With the same files,
both Ghostscript and Adobe Reader produce PS that prints fine.

-- Juliusz
Comment 6 Markus Duft 2008-05-04 23:12:50 UTC
(In reply to comment #5)
> I've noticed this too.  Something is wrong with the way pdftops embeds bitmaps
> in PostScript, it causes printers to run out of memory.  With the same files,
> both Ghostscript and Adobe Reader produce PS that prints fine.
> -- Juliusz

Yes, that the same thing as i see, except that i have no bitmaps. i have just text, and some bar-codes (may that be embedded as bitmap? i think so, hm?)
Comment 7 GitLab Migration User 2018-08-21 10:55:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/431.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.