Print job could not be executed
This document (7018837) is provided subject to the disclaimer at the end of this document.
To get what the application submits to CUPS do the following:
- Stop printing for your print queue. As user 'root' run "cupsdisable <queue_name>" (replace <queue_name> with your print queue name).
- As normal user print the exact example file where printing fails from the particular application program.
- What the application had submitted in the previous step to CUPS is now hold in the print queue as "/var/spool/cups/d<job_number>-<id>" (replace <job_number> and <id> with correct print job number's)
- Save the print job data for further analysis. As user 'root' run "cp /var/spool/cups/d<job_number>-<id> /tmp/print-job-data.save" and "chmod a+r /tmp/print-job-data.save" to make it accessible also as normal user for later analysis.
- Re-enable printing for your print queue. As user 'root' run "cupsenable <queue_name>".
- Now "/tmp/print-job-data.save" can be inspected.
- Verify if print job data is PostScript or PDF: "file /tmp/print-job-data.save".
- Display print job data with Ghostscript: "gs -r50 -sPAPERSIZE=a4 -dFIXEDMEDIA /tmp/print-job-data.save"
- For the case the print job data were created successfully, make sure to have the latest firmware installed on the printer device and test again.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7018837
- Creation Date: 27-Apr-2017
- Modified Date:03-Mar-2020
- SUSE Linux Enterprise Desktop
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com