Edit ----> using “PCL 6 Emulation” on printer
And PCL generic driver on CUPS, the other Emulations belong to very old Printers
it sends something to the printer but the print stops at the processing phase and never prints
CUPS LOGS :
D [17/Nov/2022:00:33:31 +0200] [Job 24] Device protocol: 2
D [17/Nov/2022:00:33:31 +0200] [Job 24] Sending data to printer.
D [17/Nov/2022:00:33:31 +0200] [Job 24] Read 4 bytes of print data…
D [17/Nov/2022:00:33:31 +0200] [Job 24] Wrote 4 bytes of print data…
D [17/Nov/2022:00:33:31 +0200] [Job 24] Sent 4 bytes…
D [17/Nov/2022:00:33:31 +0200] [Job 24] Waiting for read thread to exit…
D [17/Nov/2022:00:33:31 +0200] [Job 24] PID 4365 (/usr/lib/cups/backend/usb) exited with no errors.
D [17/Nov/2022:00:33:31 +0200] [Job 24] End of messages
D [17/Nov/2022:00:33:31 +0200] [Job 24] printer-state=3(idle)
D [17/Nov/2022:00:33:31 +0200] [Job 24] printer-state-message=“Sending data to printer.”
D [17/Nov/2022:00:33:31 +0200] [Job 24] printer-state-reasons=none
CUPS: "Filter failed"
A "filter failed" error can be caused by any number of issues. The CUPS error log (by default /var/log/cups/error_log) should record which filter failed and why.
I believe ubuntu was using PCL 6 Driver (I was a stupid linux user at that time ) but for some odd reason it doesn’t work on arch …
. I use windows 10 to print projects now
Stupid questions I know. Is the printer plugged in, connected and turned on?
And did you set up the printer to work with the program you’re printing from?
And did you restart the computer after installing the driver?
I did A Hard - Restart Evey Time (It means OS Goes Throught POST process eveytime) I Used New Driver
and I did Make The Printer Use PCL 6 Emulation
… printer connected throught usb
I figured as much, but its often the stupid things that people do that cause the most problems so it never hurts to eliminate them first.
One last thing to try is to go to the printer itself and see if you can print directly from the machine, I’m not familiar with Kyocera but my old Epson sometimes needed a nudge. As it’s possible the job is trapped in the print spooler.
OK, we’ve eliminated the computer and the driver from being the problem. They’re working fine, your printer is getting the information just not doing its job.
Now that you have cleared the spooler, try turning the printer off and wait about 30 - 40 seconds before turning it back on. The time is more than necessary, but it’s best to make sure everything clears from memory. Next check that the settings on the printer are correct.
Without being there to tech the machine personally, the only thing from here that I can recommend is to go to Keyocera’s website and see if they have a solution.