#1 2016-09-05 07:41:35

Vytautas

Member

Registered: 2016-01-17

Posts: 27

Printing stops at "Processing - Spooling job, 42% complete."

I am trying to connect to an EPSON AL-MX20 printer on a Windows network.

Printing stops at "Processing - Spooling job, 42% complete."
Then the message is shown: "Unable to locate printer."

Could you please make suggestions how could I fix that?

I tried installing printer in two ways:
1) through CUPS, using epalmx20.ppd,
2) using openprinting-ppds-postscript-epson_20130226-1lsb3.2_all.deb file.

Errors are the same with both installations. The printer is on and works from Windows.

If I write an address:
dnssd://192.168.1.X/
in place of
dnssd://AL-MX20-4F1D3F._printer._tcp.local/

Then I get Printer State: Idle, Processing... But printing does not starts too.

Last edited by Vytautas (2016-09-05 07:54:37)

Kasey00

Banned

Registered: 2019-12-23

Posts: 3

Re: Printing stops at "Processing - Spooling job, 42% complete."

I am trying to connect to an EPSON AL-MX20 printer on a Windows network.

Printing stops at "Processing - Spooling job, 42% complete."
Then the message is shown: "Unable to locate printer."

Could you please make suggestions how could I fix that?

I tried installing printer in two ways:
1) through CUPS, using epalmx20.ppd,
2) using openprinting-ppds-postscript-epson_20130226-1lsb3.2_all.deb file.

Errors are the same with both installations. The printer is on and works from Windows.

If I write an ipage  address:
dnssd://192.168.1.X/
in place of
dnssd://AL-MX20-4F1D3F._printer._tcp.local/

Then I get Printer State: Idle, Processing... But printing does not starts too.

Maybe te memory unit of your printer is damaged. You should get to a professional for this.

Last edited by Kasey00 (2019-12-24 07:47:42)

twoion

ほやほや

Registered: 2015-08-10

Posts: 2,573

Re: Printing stops at "Processing - Spooling job, 42% complete."

See first if you can collect some actual CUPS error messages following https://wiki.debian.org/CUPSDebugging, also check the systemd journal for the cups service and dmesg (trigger a couple of print jobs) for messages that could be indicative of the error source (printer communications failed - PPD not found or wrong parameters, whatever catches your eye). The error messages in the cups frontend are almost always useless.

Edit: This seems to actually be good postscript printer (https://www.openprinting.org/printer/Ep … on-AL-MX20)  requiring only a correct PPD file to work and not more arcane filters. I suppose the issue will be rooted in networking, the CUPS bonjour backend and suchlike.

Can you connect the printer using USB or a different protocol like ipp/ipps to see if that works instead?

---

At the end of the river the sundown beams