Re: [MOD] STR #4028: commandtops not robust against broken PostScript in PPD file
H. Blischke <HelgeBlischke-S0/[email protected]>
| Newsgroups | gmane.comp.printing.cups.bugs |
|---|---|
| Message-ID | <[email protected]> |
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Well, I think I succeeded in makeing an acceptable solution as the log file snippet demonstrates: I [21/Feb/2012:12:13:36 +0100] [Job ???] Request file type is application/vnd.cups-command. I [21/Feb/2012:12:13:36 +0100] [Job 1506] Adding start banner page "none". I [21/Feb/2012:12:13:36 +0100] [Job 1506] Adding end banner page "none". I [21/Feb/2012:12:13:36 +0100] [Job 1506] File of type application/vnd.cups-command queued by "helgeblischke". I [21/Feb/2012:12:13:36 +0100] [Job 1506] Queued on "OKI_DATA_CORP_C3600" by "helgeblischke". I [21/Feb/2012:12:13:36 +0100] [Job 1506] Started filter /usr/libexec/cups/filter/commandtops (PID 26740) I [21/Feb/2012:12:13:36 +0100] [Job 1506] Started backend /usr/libexec/cups/backend/usb (PID 26741) E [21/Feb/2012:12:14:07 +0100] [Job 1506] PostScript error in "?OKMediaType": stackunderflow; offending command:exch I [21/Feb/2012:12:14:29 +0100] [Job 1506] Completed successfully. But, as PostScript is a programming language, it is possible (and my test printer's PPD showed that by casting the error handling deep into systemdict as part of a query) to successfully defeat anything, so don't be too much disappointed when the printer *prints* error messages during autoconfigure or does some flimflammed things. Link: http://www.cups.org/str.php?L4028 Version: 1.5.2