Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Linux (Ubuntu/Fedora/Arch), CUPS, IPP Everywhere, Network printing

Fix CUPS “filter failed” / “backend crashed” — job stops after first page (Ubuntu, Debian, Fedora, Arch)

Technician

Hey! We’ll sort the case where CUPS prints one page then hangs and shows “Filter failed” or “Backend crash”. A couple of details help me target the fix:
• Distro & version (Ubuntu/Debian/Fedora/Arch, kernel).
• Printer model and how it’s connected (USB, IPP/IPP Everywhere, socket:// 9100).
• In /var/log/cups/error_log, what do you see around the failure (e.g., gstoraster, pdftops, rasterto..., backend usb)?
These show whether it’s a cups-filters/ghostscript issue, a bad PPD, or a crashing backend.

Customer

Ubuntu 24.04, Epson USB. First page prints, then job halts. Queue says “Filter failed”. The log mentions gstoraster and “stopped with status 1”.

Technician

Got it. That pattern (first page OK → stop) usually means a filter chain problem: gstoraster or pdftops fails mid-job, or the USB backend stalls. Common causes include:
• cups-filters ↔ ghostscript mismatch, missing foomatic-db/Gutenprint bits.
• Wrong/legacy PPD options (Resolution/ColorModel/finishing) crashing the filter.
• Disk full in /var/spool/cups or perms/AppArmor issues.
• Buggy vendor driver vs IPP Everywhere/driverless path.
We’ll confirm via logs, then patch the filter path or swap the driver.

Customer

Where exactly do I enable detailed logging? My error_log is short.

Technician

Step 1 — Turn on debug logging
Run:
sudo cupsctl --debug-logging
Then reproduce the print. Check /var/log/cups/error_log for which stage fails (gstoraster, rastertoepson, usb, ipp).
If needed, bump to debug2 in /etc/cups/cupsd.conf (LogLevel debug2) and sudo systemctl restart cups. This exposes precise filter failed reasons and backend crashes.

Customer

After enabling debug I see: gstoraster stopped with status 1 and then Job canceled because the filter failed.

Technician

Step 2 — Repair the PDF→raster path
1) Update printing stack:
sudo apt update && sudo apt install --reinstall cups cups-filters ghostscript
2) Install missing data (often needed):
sudo apt install foomatic-db foomatic-db-compressed-ppds printer-driver-gutenprint
3) Switch renderer if available in PPD:
• Set pdftops (Poppler) instead of Ghostscript (or vice versa) via printer options.
4) Re-test. If the job proceeds beyond page 1, we’ve fixed the filter failed crash path.

Customer

It still halts after page 1. The PPD is the vendor’s. Anything with USB backend?

Technician

Step 3 — Stabilize the backend
• Try driverless queue: ipp://<printer-ip>/ipp/print or ipps:// (often more reliable than legacy USB). Many Epsons work via IPP Everywhere.
• If staying on USB, swap cable/port and ensure user is in lp/lpadmin. Check dmesg for resets.
• Clear stuck jobs/enable queue:
cancel -a → cupsenable <queue> → cupsaccept <queue>.
• Confirm space/permissions:
df -h /var and ls -ld /var/spool/cups (disk full or bad perms can trigger filter failed after the first page).

Customer

Space is fine. Using vendor PPD. Any options to tweak that could crash the filter?

Technician

Step 4 — PPD/driver sanity
Mismatched options can kill filters after page 1. Test these one by one:
• Lower Resolution (e.g., 600→300 dpi) and set ColorModel to RGB or Grayscale.
• Disable duplex, finishing, or special halftones.
• If using HPLIP or ESC/P-R, reinstall the driver:
sudo apt install --reinstall hplip hplip-data or sudo apt install printer-driver-escpr.
• As a clean test, add a new IPP Everywhere queue (driverless). If it prints multiple pages, the vendor PPD was the culprit.

Customer

Driverless IPP works — multiple pages print. Can I keep USB but avoid the crash?

Technician

You can. Two approaches:
1) Keep the working IPP Everywhere queue as default (recommended for reliability).
2) Or rebuild a USB queue but with safer filters:
• Use a Gutenprint or ESC/P-R PPD instead of the vendor legacy one.
• Force renderer: if your PPD allows “pdftops”/“gstoraster”, pick the opposite of what crashed.
• Make sure cups-filters and ghostscript are current; mismatches are known to trigger filter failed.

Customer

It’s a small office. Anything else to keep CUPS stable across users?

Technician

Admin tips:
• Standardize on one queue (prefer driverless IPP) and remove old USB queues to avoid PPD conflicts.
• Monitor logs at info level; keep debug only while testing.
• On Fedora/Arch, ensure cups-filters and foomatic-db are installed; on Ubuntu, keep hplip/escpr up to date.
• Watch for /var/spool/cups growth and AppArmor/SELinux denials.

Customer

Switched to IPP Everywhere; multiple-page jobs are fine now. Thanks!

Technician

Summary: For “CUPS prints one page then hangs”, enable --debug-logging, identify the failing filter (gstoraster/pdftops) or backend, update cups-filters/ghostscript, try IPP Everywhere or a safer PPD, and verify spool/permissions. Need help parsing error_log? Open the chat.

Quick answer: the accepted fix

Accepted fix when CUPS prints one page then stops: turn on debug logging, update cups-filters and ghostscript, test a clean IPP Everywhere (driverless) queue, or swap PPD/rendering path (pdftops ↔ gstoraster). Check disk space and permissions in /var/spool/cups. This resolves most filter failed / backend crash cases.

FAQ

Step-by-step (Linux/CUPS)

1. Enable logging: sudo cupsctl --debug-logging and reprint; inspect /var/log/cups/error_log.
2. Update stack: sudo apt install --reinstall cups cups-filters ghostscript foomatic-db (use distro equivalents).
3. Add a fresh IPP Everywhere queue (ipp://<ip>/ipp/print) and test multi-page PDFs.
4. If staying USB: reinstall vendor driver or switch to Gutenprint/ESC-P-R; lower DPI/disable duplex.

Note for mixed environments (macOS/Linux)

1. Prefer IPP/AirPrint queues shared from CUPS; avoid mixing several drivers for the same device.
2. Keep CUPS and printer firmware updated; align options (paper size, duplex) across clients.

Sources

• ArchWiki — CUPS/Troubleshooting
• Ubuntu Server Docs — CUPS print server & error logs
• OpenPrinting — CUPS error_log FAQ

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.