Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#59775 - [cups-filters] "failed filter" error after upgrading to cups-filters 1.21.0-1

Attached to Project: Arch Linux
Opened by Erik Wesselius (zilverling) - Thursday, 23 August 2018, 10:55 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 25 August 2018, 17:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After a full system update this morning, my printer ceased to respond to print jobs.

Cups reported the error message "Failed filter".

In the systemd logs I found this:
ANOM_ABEND auid=4294967295 uid=209 gid=209 ses=4294967295 pid=2597 comm="foomatic-rip" exe="/usr/lib/cups/filter/foomatic-rip" sig=11 res=1

The file foomatic-rip belongs to the package cups-filters and that package was indeed updated today (to version 1.21.0-1). After downgrading cups-filters to the previous version (1.20.4-2) the printer is responding normally again. I will file this with the package maintainer.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 25 August 2018, 17:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.21.0-2
Comment by Tyler A (tyler) - Thursday, 23 August 2018, 18:51 GMT
I can confirm I had exactly the same problem with Brother HL-2240D Foomatic/hl1250

I was seeing this in my cups error_log:

(/usr/lib/cups/filter/foomatic-rip) crashed on signal 11.

Downgrading the package restored my printing abilities.
Comment by loqs (loqs) - Thursday, 23 August 2018, 19:25 GMT
Can you bisect between 1.20.4 and 1.21.0 and find the causal commit?
722fee6ab541abd25699f9ed67f610612c857166 and fc6a67dfbfc7346e80bd48a0d6ddc858afcabcdf are the only direct changes to foomatic-rip.
Comment by Erik Wesselius (zilverling) - Friday, 24 August 2018, 08:23 GMT
@loqs - Found page on bisecting on the Arch Linux wiki. Will see how far I can get with that over the weekend.

@tyler: That's exactly the same error message that I get. As a result of that error my printer -- a trusted, over 15 years old Kyocera FS-1000 -- doesn't receive the job.
Comment by Andreas Radke (AndyRTR) - Friday, 24 August 2018, 11:10 GMT
Looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907026 - please help upstream to fix it.
Comment by loqs (loqs) - Friday, 24 August 2018, 11:20 GMT
using the attached PKGBUILD as I could not find one in AUR for cups-filters-git

cd cups-filters-git
makepkg -o
cd src/cups-filters
git checkout a46189488750ff150abd7168b2e882cdabba8da4 #this commit is used instead of 1.20.4 because it includes the patch for poppler 0.64.0
autoreconf -fi
cd ../..
makepkg -ersi #check this version works

cd cups-filters-git
cd src/cups-filters
git checkout release-1-21-0
autoreconf -fi
cd ../..
makepkg -ersi #check this version fails

cd cups-filters-git
cd src/cups-filters
git bisect start
git bisect good a46189488750ff150abd7168b2e882cdabba8da4
git bisect bad release-1-21-0
autoreconf -fi # [1]
cd ../..
makepkg -ersi #see if this version fails

cd cups-filters-git
cd src/cups-filters
git bisect $result #substitute good or bad for $result depending on result of last version repeat back to # [1] until git has found the bad commit
Comment by Erik Wesselius (zilverling) - Friday, 24 August 2018, 19:38 GMT

Loading...