Bug 25020 - foomatic-rip error "Unable to determine number of pages, page count: -1"
Summary: foomatic-rip error "Unable to determine number of pages, page count: -1"
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2019-06-29 11:52 CEST by Dan Fandrich
Modified: 2023-08-18 15:32 CEST (History)
4 users (show)

See Also:
Source RPM: cups-filters-1.13.4-2.2.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Dan Fandrich 2019-06-29 11:52:27 CEST
Description of problem:
Printing to a CUPS printer backed by foomatic-rip (HP DJ720c for example) fails and returns the error "Unable to determine number of pages, page count: -1" in the journal. This includes trying to print using CUPS' built-in "Print Test Page" function. This started happening some time in the last month or two and it always fails now. I'm guessing it happened after installing ghostscript 9.26-1.4.mga6

This appears to be the same issue as https://bugs.archlinux.org/task/62251 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926576 although my Ghostscript version is 9.26, but the latest mga6 version appears to include a bunch of security patches from upstream that likely cause this problem.

I was able to fix the problem on my machine by building foomatic-rip from cups-filters-1.22.5 (which requires a newer qpdf than is in mga6 so I built 
qpdf-8.4.2 and linked it statically) and replacing the binary in /usr/lib/cups/filter/foomatic-rip

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

How reproducible:
It happens when printing from all tested applications. Printing to a different, non-foomatic printer works fine.

Steps to Reproduce:
1. Choose a Foomatic printer at http://localhost:631/printers/ and select "Print Test Page"
2. Note the error: stopped "Filter failed"
3. Check the journal for more detailed errors: sudo journalctl -u cups -b
Comment 1 Lewis Smith 2019-06-30 22:03:18 CEST
Assigning to Thierry initially, as registered maintainer for cups-filters.

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

Comment 2 Morgan Leijström 2019-06-30 23:47:49 CEST
Yes, the update to ghostscript-9.26 bug 24786 seem to have removed some deprecated functions so some printers do not work anymore.

I have a similar problem but had no time to dig into it yet:  https://forums.mageia.org/en/viewtopic.php?p=75161#p75161

I also have the same problem trying in mga7.  Have you tried?

CC: (none) => fri

Comment 3 Dan Fandrich 2019-07-01 21:37:23 CEST
This is probably the same issue as bug 24786 comment 7. I haven't tried this in mga7 but since it contains cups-filters-1.22.5 I wouldn't expect it to be affected.
Comment 4 Aurelien Oudelet 2020-08-23 15:17:26 CEST
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:OLD

Status: NEW => RESOLVED
Keywords: (none) => UPSTREAM
CC: (none) => ouaurelien
Resolution: (none) => OLD

Comment 5 Morgan Leijström 2020-08-28 17:23:32 CEST
Well as i reported in c2 it was in mga7 too.
The solution came when printer manufacturer finally got around to updating the driver to not use the deprecated functions.

So the bug was several main printer manufacturers being far behind in their driver developent.

Version: 6 => 7

Aurelien Oudelet 2020-08-28 18:23:25 CEST

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Morgan Leijström 2020-08-28 18:26:12 CEST

Hardware: i586 => All

Comment 6 Aurelien Oudelet 2021-07-06 13:16:49 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 7 Marja Van Waes 2021-09-07 14:10:12 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: REOPENED => RESOLVED
Resolution: (none) => OLD

Comment 8 aric joshua 2021-09-14 14:15:06 CEST Comment hidden (spam)

CC: (none) => aricjoshua44

Comment 9 portaitheap portaitheap 2022-01-24 19:44:46 CET Comment hidden (spam)

CC: (none) => nillremilton

Dave Hodgins 2022-01-24 20:41:03 CET

CC: nillremilton => davidwhodgins

Comment 10 Martin Daert 2022-04-21 21:21:09 CEST Comment hidden (spam)

CC: (none) => banasher336

Comment 11 Phil Reacher 2022-07-16 10:19:14 CEST Comment hidden (spam)

CC: (none) => philreacher1991

Comment 12 Saint Otis 2023-06-13 05:27:05 CEST Comment hidden (spam)

CC: (none) => SaintOtis12

sturmvogel 2023-06-13 06:14:15 CEST

CC: SaintOtis12, aricjoshua44, banasher336, philreacher1991 => (none)

Comment 13 robertjace robertjace 2023-07-06 09:27:33 CEST Comment hidden (spam)

CC: (none) => robertjace512

sturmvogel 2023-07-06 15:41:12 CEST

CC: robertjace512 => (none)

Comment 14 Mark Halland 2023-08-18 13:42:24 CEST Comment hidden (spam)

CC: (none) => markhalland905

sturmvogel 2023-08-18 15:32:37 CEST

CC: markhalland905 => (none)


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