Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #3493
| From | ken <ken@spamcop.net> |
|---|---|
| Newsgroups | comp.lang.postscript |
| Subject | Re: Possible ghostscript error interfering with printing in Linux MInt |
| Date | 2020-01-31 19:52 +0000 |
| Message-ID | <MPG.389e95becbf624949898af@usenet.plus.net> (permalink) |
| References | <fdde25db-89cf-45e8-98d9-e0a7cdef20f7@googlegroups.com> |
In article <fdde25db-89cf-45e8-98d9-e0a7cdef20f7@googlegroups.com>, ken@balglaze.myzen.co.uk says... > Can anyone explain the ghostscript error and suggest how to overcome eit? You don't have the real Ghostscript error message there, just the error code which is what it says, a fatal error. I believe its possible to get CUPS to log the Ghostscript back channel to get the real error message, but I can't recall how to do that. I think there might be instructions somewhere. Hmm you could try this URL: https://wiki.ubuntu.com/DebuggingPrintingProblems and look for CUPS error_log where it has instructions for setting the logging level. If you make the file available I can look at the problem (since you have given the command line). I doubt you can 'overcome it', most likely either the input file is damaged or its a Ghostscript bug. I should note that you are not using the most up to date version of Ghostscript, and there are known security problems with the version you are using. Ken
Back to comp.lang.postscript | Previous | Next — Previous in thread | Find similar
Possible ghostscript error interfering with printing in Linux MInt ken@balglaze.myzen.co.uk - 2020-01-31 06:34 -0800 Re: Possible ghostscript error interfering with printing in Linux MInt ken <ken@spamcop.net> - 2020-01-31 19:52 +0000
csiph-web