Bug 21424 - CUPS 2.2.4 "Filter failed" and failure of some programs to recognise installed printer
Summary: CUPS 2.2.4 "Filter failed" and failure of some programs to recognise installe...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High critical
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard: MGA6TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-31 20:32 CEST by aguador
Modified: 2017-08-07 13:49 CEST (History)
3 users (show)

See Also:
Source RPM: cups-2.2.4-1.mga7.x86_64
CVE:
Status comment:


Attachments

Description aguador 2017-07-31 20:32:25 CEST
Description of problem:

When trying to print from LibreOffice and qpdf, the installed printer is no longer recognized. No printer is listed in qpdf, "generic printer" in LO.

Tests with Evince, Leafpad and Tomboy Notes showed the installed printer, but printing failed with the "Filter failed" message in Cups and (sometimes) the printing dialogue of the programs. With these programs the printer does awaken, but does not print.

I tried setting "LogLevel debug" in /etc/cups/cupsd.conf, but no debug log was generated.

I can confirm that avahi is running and, obviously, cups (localhost:631) sees the printer correctly.

System details: Fully up-to-date 86_64 Cauldron installation with E21 and a Brother DPW-7055W printer printing from the USB connection.

I have changed no printer settings and had no problems printing with cups-2.2.3-2 on this machine, and still have no problem printing from my Mga6 machine with cups-2.2.3-2.

How reproducible:
Update to CUPS 2.2.4 and attempt to print from any program.
Comment 1 David Walser 2017-07-31 22:42:18 CEST
Please test Mageia 6 with CUPS 2.2.4-1.mga6 from core/updates_testing to see if you can also reproduce an issue.  That will help us narrow down if the problem is in CUPS itself or something else in Cauldron.
Comment 2 aguador 2017-08-01 00:31:02 CEST
Why can't these thing be clear?!?

With the cups from testing in mga6, LO shows "generic printer" and qpdf no printer.

However, printing works from both Evince and Tomboy Notes.

Oops, my bad. As I was getting set to revert to 2.2.3 I have seen that libcups2-2.2.3 is still there while mga7 has libcups2-2.2.4. Perhaps the problem lies there?

[I hate to say this, but I leave on vacation early tomorrow AM, so David, if you or anyone else sees this and would like me to do more, I will need to know in about 5 hours. After that I will be without a good Internet connection for a while!]
Comment 3 aguador 2017-08-01 01:16:44 CEST
PS After shutting down I realised that I updated my Mga6 system so was operating on the new 4.9.40 kernel. So . . .

I checked in mga7 with the 4.9.39 kernel and. . . no go with LO.

In mga6 with both the 4.9.35 and 4.9.40 kernels . . . no go with LO and that after I had downgraded to cups-2.2.3. (Good thing I won't be using my printer for a while!)

Hope this helps.
Comment 4 aguador 2017-08-01 06:29:39 CEST
Stupid me: I downgraded cups, but not cups common or lib64cups2. After downgrading from all version 2.2.4 cups packages, fully updated Mga6 prints properly. It would seem that something is definitely going on with cups-2.2.4.
Comment 5 Marja Van Waes 2017-08-01 16:26:52 CEST
(In reply to Roy Reese from comment #4)
> Stupid me: I downgraded cups, but not cups common or lib64cups2. After
> downgrading from all version 2.2.4 cups packages, fully updated Mga6 prints
> properly. It would seem that something is definitely going on with
> cups-2.2.4.

OK, so everything works fine again after downgrading all cups packages to 2.2.3-2

Assigning to the cups maintainer.

Assignee: bugsquad => thierry.vignaud
CC: (none) => marja11

Rémi Verschelde 2017-08-02 08:35:34 CEST

Blocks: (none) => 21168

Comment 6 James Kerr 2017-08-02 16:26:14 CEST
I confirm that there is a problem.

LO shows the printer in the Print dialogue and HPLIP reports that the file has been printed, but sometimes the file is not printed. Even when it has been printed CUPS web interface does not report it as a completed job, but as "Stopped - filter failed"

Ocular fails to print .pdf files (even one which has been printed in LO - Draw) although the HP notification reports the file as having been printed.

I have not seen this problem in Mageia 6 with cups-2.2.4 from testing.

CC: (none) => jim

Comment 7 James Kerr 2017-08-02 16:48:08 CEST
I note that in Mageia 6 we have cups-filters-1.13.4 but in cauldron we have cups-filters-1.14.1. Perhaps that's a pointer to the source of the problem.
Rémi Verschelde 2017-08-02 16:50:04 CEST

Blocks: 21168 => (none)

Comment 8 Rémi Verschelde 2017-08-04 13:31:24 CEST
So apparently this does affect Mageia 6 with the newly pushed 2.1.4 update (bug 21168), though obviously it did not affect our QA testers.

Reports on the discuss@ ML indicate:

> Printing from Kwrite produces a blank page with cups 2.2.4-1 64bit on Mageia 6.
> A test page from MCC works but produces a message "Processing filter failed" while printing...

> I find in my syslog lines like this each time a blank page is printed:
> Aug  4 11:52:34 optix kernel: [11819.392238] pdftopdf[21315]: segfault at 10 ip 00007f0c5bfd7c63 sp 00007ffefa538180 error 6 in libc-2.22.so[7f0c5bf5b000+1a9000]

Severity: normal => critical
Whiteboard: (none) => MGA6TOO
Priority: Normal => High

Comment 9 Rémi Verschelde 2017-08-04 13:32:43 CEST
*** Bug 21444 has been marked as a duplicate of this bug. ***

CC: (none) => andresalaun

Comment 10 David Walser 2017-08-04 21:35:51 CEST
If you're running Cauldron, please test with the cups-filters rebuild (cups-filters-1.14.1-2.mga7) and see if it helps.
Comment 11 James Kerr 2017-08-05 07:23:25 CEST
rpm -q cups-filters
cups-filters-1.14.1-2.mga7

LO, kwrite and okular print consistently

CUPS web interface correctly reports completed jobs and there are no more "filter failed" reports.

This rebuilt package fixes printing problems for me with HP Envy 4502 on cauldron.
Comment 12 Rémi Verschelde 2017-08-07 13:49:34 CEST
Awesome! Now let's do the same fix for bug 21444 in Mageia 6.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


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