Printing of subsequent documents can fail often.

Today I printed another PDF file by the program “evince 3.24.0-1.2” from within my XFCE session at first glance successfully.

I tried then to print a mail by the program “Mozilla Thunderbird 52.2.1-1.5”. But this printer “Kyocera P6021cdn (KPDL)” provided only the following unexpected output.

)
 %%EndComments
              %%BeginProlog
                           %%BeginResource: procset xpdf 3.00 0
                                                               %%Copyright: Co

I powered the printer off for a moment and switched it on again. I could print the same mail then repeatedly without the shown extra data after the printer restart.

Which components would need another system correction besides the software “CUPS 2.2.3-211.2”?

Without much investigation,
Standard Operating Practice would be to purge the Print Queue, then send the print jobs again.
Depending on your setup and configurations, there may be print queues in the printer, any machine acting as a Print Server including the machine the printer is attached to (if it’s not a Network Printer) and the PC that created the original print job.

TSU

I am going to repeat them after a printer reboot.

How often do you observe that subsequent print tries will usually fail after the first printout?

What you’re describing could very well be a printer firmware issue. If you also rebooted your computer ( without telling here ) a lot more would be involved.

How much can unwanted effects be clarified around this software component?

Restarting a printer makes it (re)load it’s firmware as well. Since ‘rebooting’ the printer solved your issue, that’s my 2 cents.

Similar behaviour for same model reported here
https://superuser.com/questions/896712/printer-kyocera-p602cdn-randomly-prints-out-postscript-code
See if one of the suggestions posted there work for you.

It looked easier for me to press the power button for the device on the desktop occasionally. I find my intermediate solution still strange.

The model identifier is P6021cdn in my case. Thanks for your link to an other clarification request on the topic “Printer (Kyocera P602cdn) randomly prints out postscript code”.
My usage situation might be similar.

How challenging would it become to check the failure rate of the involved software components in more detail by a corresponding system test script?

Try the recommendations given in that thread. Which emulation setting is currently configured in your printer? If ‘KPDL (Auto)’ is configured, try setting ‘KPDL’ as suggested in the second answer given there.

Can other components be already excluded from their contribution to the mentioned printing hiccups?

Which emulation setting is currently configured in your printer?

The device display showed the following information.


>Emulation
  PCL 6

How much will the print jobs influence the corresponding data processing interface?

Would you like to be able to select an other setting by a dialogue like “Printer Properties”?

Ok, the printer is configured to accept PCL 6. So, I assume that you’re using a PCL driver? Is this the vendor-supplied driver, or an openprinting driver? I assumed from your first post that KPDL (PostScript) was being used, and the output snippet you shared looked like PS code being printed (as opposed to the document expected).

For troubleshooting, I can only offer general advice. I don’t own such hardware. These may be helpful to you.
https://en.opensuse.org/SDB:CUPS_in_a_Nutshell
https://fedoraproject.org/wiki/How_to_debug_printing_problems

Yes. - But it seems to be only an ordinary PPD file.

or an openprinting driver?

No. - Can the support become better by information from the OpenPrinting database?
My model is not provided by the package “OpenPrintingPPDs-postscript 4.0.0.2-4.1”.

I assumed from your first post that KPDL (PostScript) was being used,

…
*FileVersion: "8.1308"
…
*PSVersion: "(3011.103) 1"
…
*NickName: "Kyocera ECOSYS P6021cdn (KPDL)"

*PCFileName: "KC5150EG.PPD"
…

and the output snippet you shared looked like PS code being printed (as opposed to the document expected).

Do I need to trigger any more questionable “printer resets” for the desired outputs?

It seems that that my printing surprises can eventually still continue also with an available software alternative.

…
*FileVersion: "8.4511"
…
*PCFileName: "KC5150EE.PPD"
…

How would you interpret another unexpected output like the following after an attempt for a version update?

Error Name:          /undefined
Offending Command:   Pages:


Operand Stack:

  1. What happens if you set KPDL emulation explicitly in the printer?

  2. The printer model may not be explicitly supported, but using generic PCL 6 or PS configuration should be compatible IMO.

  3. If none of the suggestion given in the link I provided work for you, then consider submitting a bug report I guess.

I switched to this setting yesterday.

I imagine that the current value will not matter there if the submitted print jobs will adjust such a parameter already to their needs.

  1. The printer model may not be explicitly supported, but using generic PCL 6 or PS configuration should be compatible IMO.

This model is supported to some degree. I have got an impression that the corresponding software quality is questionable once more.

  1. If none of the suggestion given in the link I provided work for you, then consider submitting a bug report I guess.

I am curious on how the involved software developers (or product maintainers) can and will care for remaining issues at all.

Since you’re using a vendor-supplied driver, perhaps worth contacting Kyocera for the required support.

I would like to be a bit more sure on how the printer software can be still questionable also in my use case.

Are there any chances that an other “PostScript Printer Description” will work better for my needs?

perhaps worth contacting Kyocera for the required support.

This would be generally possible.

:\ Expectations for a nicer product lifecycle might not fit together.

The effectiveness in achieving improvements is also varying in affected areas.

Don’t know - it’s something that you’ll have to try for yourself.

Will other discussion places help more to share corresponding experiences for better PostScript printer descriptions?