Cannot print: cfFilterchain ghostscript exited with no errors

[spacecase-25]

after running the latest update, I can no longer print. I get the error in the subject of the post and then “waiting for printer to become available” I haven’t changed anything other than running updates.

EDIT: This actually happened to my work computer as well, with the update previous to the latest update. But I figured it was an issue with the driver for the new label printer I had picked up, however now that it’s happening on my home computer with a printer that was previously working… clearly it’s a Manjaro issue.

EDIT: Further info… I am able to print to a printer over the network. Both printers that I’m having issues with are connected via USB. The network printer throws the same ghostscript error, but does print.

OK THEN… I got it to print with some turning off and turning back on… I truly have no idea what’s going on here. I will leave topic open for a little while to see if anyone has insight, as I still have that label printer at work that does not print.

[cscs]

Same … but kinda reverse.

Networked printer suddenly broke, readding and rebooting didnt help.

Wired (dymo) label printer works fine.

no ideas yet

Can't resume cups printing

I actually ran into a set of broken printing on another system yesterday, a canon pixma m920 … I couldnt investigate fully, but it may have had nothing to do with the device or drivers, as I attempted re-adding multiple ways (gutenprint, driverless, cijfilter, etc)… but printing failed on all attempts, either from ‘cannot locate printer’ or some other pstopdf/ghostscript ‘exited’ non-error without printing. Sorry to not be of more help just now. But I might be back

@spacecase-25

OK THEN… I got it to print with some turning off and turning back on… I truly have no idea what’s going on here.

Some goodness then. No such luck here. I guess Ill pull the power a few more times.

[morrisjm]

FWIW I have this error on Ubuntu 23.10 / Canon MX870. Only happens with pdfs; from LibreOffice I can print fine (making it seemingly a ghostscript issue, consistent with the status). Same system was working fine last week.