Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1627834 - hpcups results in "Filter failed" for HP OfficeJet Pro 6970
Summary: hpcups results in "Filter failed" for HP OfficeJet Pro 6970
Keywords:
Status: CLOSED DUPLICATE of bug 1626818
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: 28
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-11 16:07 UTC by Stefan Schwarzer
Modified: 2018-09-11 16:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-11 16:12:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
troubleshoot.log as exported from the print problem diagnostic tool (32.38 KB, text/plain)
2018-09-11 16:07 UTC, Stefan Schwarzer
no flags Details
Journal for CUPS while a job was printed that resulted in the described error (221.49 KB, text/plain)
2018-09-11 16:11 UTC, Stefan Schwarzer
no flags Details

Description Stefan Schwarzer 2018-09-11 16:07:28 UTC
Created attachment 1482398 [details]
troubleshoot.log as exported from the print problem diagnostic tool

Description of problem:

I bought an HP OfficeJet Pro 6970. The printer works both as a network printer or attached to the computer via USB.

When printing with the recommended hpcups driver, the job prints fine with good results. However, at the end of the job, a error messagebox appears, saying the print job failed ("Print Error There was a problem processing document ..."). The Diagnose button only suggests looking at the journal entries.

When inspecting the attributes of the failed job via the GUI, I notice the value `job-printer-state-message` set to "Filter failed". The job has to be explicitly deleted to remove it from the job list.


Version-Release number of selected component (if applicable):

hplip is version 3.18.6-1.fc28 .


How reproducible:

Always, as far as I can tell. With the printer set up as a network printer, I got the above behavior for the test page in the printer configuration, when printing a web page from Firefox or when printing a PDF from the command line with `lp`.


Steps to Reproduce:
1. Use `system-config-printer` to add the printer as a network printer (adding it as a USB printer reproduces the bug as well). Choose the suggested printer and then the recommended driver ("HP Officejet Pro 6970, hpcups 3.18.6 [en] (recommended)").
2. Adjust printer options (e. g. page format) as necessary.
3. Print test page.
4. The page prints fine, but a messagebox appears saying there was a problem. Jobs must be removed explicitly.


Actual results:

See description.


Expected results:

The job should print without error messages. Finished jobs should be removed from the job queue automatically.


Additional info:

I tried the following to find out more and potentially get rid of the problem:

- Installed the printer as an USB printer, not a network printer. The problem still occurred.
- Set up the printer with `hp-setup` (worked only as a USB printer). The problem still occurred.
- Deactivated firewall and SELinux (set to not enforcing) before printing. The problem still occurred.
- In addition to printing the test page from `system-config-printer`, printed a web page from Firefox and a PDF from the command line with `lp`. The problem still occurred in all these cases.
- Tried the second driver for the printer ("Generic PCL 3 Printer Foomatic/pcl3 (recommended)"). The error message after printing disappeared, but the test page looks awful.
- Tried the third driver for the printer ("HP Officejet Pro 6970 hpijs, 3.18.6"). The error message after printing disappeared and the output looks fine, but often (or always?) the printer ejects a blank page after the job.
- With the first, recommended, driver used https://fedoraproject.org/wiki/How_to_debug_printing_problems#Getting_debug_logging_from_journal to enable debug logging (later changed this to log level `debug2` in `cupsd.conf` and restarted cups). I got the message, "Job stopped due to filter errors; please consult the error_log file for details.", but there were no specific messages that hinted at which filter caused the problem (I found nothing in the journal or in `error_log`). I'm going to attach the log output for one of the failed print jobs.

At the moment I don't have a workaround that allows me to ignore the problem. Either I have to "click away" the error message or I have to sort out blank pages after printing. Even if noone knows a proper fix, I'd be thankful for a way to at least silence the error, so I don't have to confirm it everytime I print.

Comment 1 Stefan Schwarzer 2018-09-11 16:11:53 UTC
Created attachment 1482399 [details]
Journal for CUPS while a job was printed that resulted in the described error

There's a line "Job stopped due to filter errors; please consult the error_log file for details.", but there don't seem to be any messages that point to the problematic filter.

The file `/var/log/cups/error_log` is empty, as it should be according to the remark at the start of section https://fedoraproject.org/wiki/How_to_debug_printing_problems#Getting_debug_logging_from_journal . Since this is on Fedora 28, the CUPS errors should go into the journal. At least that's my understanding of the paragraph.

Comment 2 Zdenek Dohnal 2018-09-11 16:12:36 UTC
Hi Stefan,

thank you for reporting this issue! This is an error of ghostscript reported as https://bugzilla.redhat.com/show_bug.cgi?id=1626818. Closing as duplicate.

*** This bug has been marked as a duplicate of bug 1626818 ***

Comment 3 Stefan Schwarzer 2018-09-11 16:22:33 UTC
Hi Zdenek,

Wow, that was quick. :-) So I hope this will be fixed soon.

Now I'm sad I invested so many hours, and I'm glad that the bug is known and has a fix. :-)

Comment 4 Zdenek Dohnal 2018-09-11 16:30:45 UTC
Sorry :) , but kudos for doing all research and finding the wiki page for debugging :)

*** This bug has been marked as a duplicate of bug 1626818 ***


Note You need to log in before you can comment on or make changes to this bug.