FS#21502 - [cups] Xerox Phaser 6110MFP (network) with splix prints only 1st page
Attached to Project:
Arch Linux
Opened by Fabio Zanini (iosonofabio) - Wednesday, 27 October 2010, 21:03 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 28 October 2010, 19:56 GMT
Opened by Fabio Zanini (iosonofabio) - Wednesday, 27 October 2010, 21:03 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 28 October 2010, 19:56 GMT
|
Details
Description:
My network printer, XEROX Phaser 6110MFP, connected by static IP and splix driver, does only print the first page correctly since cups 1.4 (presumably). All other pages are garbage (the title is repeated three times, etc.). OT: I *could* print just every document by continuously opening print dialogs and print every single page by itself (as I have already done), but it tends to get on my nerves on page 91... Additional info: * package version(s) cups 1.4.4-3 libcups 1.4.4-3 lib32-libcups 1.4.4-5 splix 2.0.0-7 evince-gtk 2.30.3-1 * config and/or log files etc. The logs look ok, no error or similar, the printer seems to go banana without telling anyone. Probably not related to cups-usblp, because I do not connect via USB. Steps to reproduce: Try to print a PDF e.g. via evince-gtk, select manually pages 1,2, and print. Alternatively, select only odd pages or similar. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Thursday, 28 October 2010, 19:56 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#21388
Thursday, 28 October 2010, 19:56 GMT
Reason for closing: Duplicate
Additional comments about closing:
for _pg in {1..NN}; do lp -o page-ranges=${_pg} filename.pdf; done
works ok?
FS#21388) was the culprit. A simple downgrade to 8.71-3 fixed it. Hope that helps.[djgera]
It works as from THAT command line, for the simple reason that you create a new print job for every page. It a feasible workaround, but does not solve the problem. Thanks anyway.
[xduugu]
Oh yes man, reverting to ghostscript 8.71-3 and libspectre 0.2.6-1 (needed by evince-gtk) solves the issue. your bug report is still open, I'm having a look upstream now.
The bug report can be closed now, as it becomes a duplicate of
FS#21388.