Filter Failed (ipp) error in CUPS BionicPup64 (Workaround)

[vtpup]

Okay (all performed with fresh puppys, pfix=ram):

1.) BionicPup32 with Phaser 6000b 32 bit driver, direct connected to USB: printer works.
2.) BionicPup64, CUPS same driver and USB : doesn't work
3.) BionicPup64, CUPS same driver and USB plus Bionicpup64 32 bit compatibility sfs: doesn't work

relevant CUPS Error messages from 3.):

Code: Select all

I [18/Sep/2020:14:22:07 -0400] [Job 3] Queued on "Dell_1250c_Color_Printer" by "anonymous".
I [18/Sep/2020:14:22:07 -0400] [Job 3] Started filter /usr/lib/cups/filter/bannertopdf (PID 15547)
I [18/Sep/2020:14:22:07 -0400] [Job 3] Started filter /usr/lib/cups/filter/pdftopdf (PID 15548)
I [18/Sep/2020:14:22:07 -0400] [Job 3] Started filter /usr/lib/cups/filter/gstoraster (PID 15549)
I [18/Sep/2020:14:22:07 -0400] [Job 3] Started filter /usr/lib/cups/filter/xrhkazmf (PID 15550)
I [18/Sep/2020:14:22:07 -0400] [Job 3] Started backend /usr/lib/cups/backend/usb (PID 15551)
I [18/Sep/2020:14:22:07 -0400] [Job 3] Hint: Try setting the LogLevel to "debug" to find out more.
E [18/Sep/2020:14:22:07 -0400] [Job 3] Unable to open raster stream - : Broken pipe
I [18/Sep/2020:14:22:07 -0400] [Job 3] Hint: Try setting the LogLevel to "debug" to find out more.
E [18/Sep/2020:14:22:07 -0400] [Job 3] Job stopped due to filter errors; please consult the error_log file for details.
D [18/Sep/2020:14:22:07 -0400] [Job 3] The following messages were recorded from 14:22:07 to 14:22:07
D [18/Sep/2020:14:22:07 -0400] [Job 3] Applying default options...
D [18/Sep/2020:14:22:07 -0400] [Job 3] hold_until=0
D [18/Sep/2020:14:22:07 -0400] [Job 3] time-at-processing=1600453327
D [18/Sep/2020:14:22:07 -0400] [Job 3] 4 filters for job:
D [18/Sep/2020:14:22:07 -0400] [Job 3] bannertopdf (application/vnd.cups-pdf-banner to application/pdf, cost 32)
D [18/Sep/2020:14:22:07 -0400] [Job 3] pdftopdf (application/pdf to application/vnd.cups-pdf, cost 66)
D [18/Sep/2020:14:22:07 -0400] [Job 3] gstoraster (application/vnd.cups-pdf to application/vnd.cups-raster, cost 99)
D [18/Sep/2020:14:22:07 -0400] [Job 3] /usr/lib/cups/filter/xrhkazmf (application/vnd.cups-raster to printer/Dell_1250c_Color_Printer, cost 0)

And the same with debug set to "on"

Code: Select all

D [18/Sep/2020:14:38:20 -0400] [Job 3] Start rendering...
D [18/Sep/2020:14:38:20 -0400] [Job 3] Processing page 1...
D [18/Sep/2020:14:38:20 -0400] [Job 3] PID 21302 (/usr/lib/cups/backend/usb) exited with no errors.
D [18/Sep/2020:14:38:20 -0400] [Job 3] Error: /ioerror in --showpage--
D [18/Sep/2020:14:38:20 -0400] [Job 3] Operand stack:
D [18/Sep/2020:14:38:20 -0400] [Job 3] true   (/var/spool/cups/tmp/gs_Bkh1Xc)   --nostringval--   1   true
D [18/Sep/2020:14:38:20 -0400] [Job 3] Execution stack:
D [18/Sep/2020:14:38:20 -0400] [Job 3] %interp_exit   .runexec2   --nostringval--   showpage   --nostringval--   2   %stopped_push   --nostringval--   showpage   showpage   false   1   %stopped_push   2043   2   3   %oparray_pop   2042   2   3   %oparray_pop   2023   2   3   %oparray_pop   showpage   2024   4   3   %oparray_pop   showpage   showpage   2   1   1   showpage   %for_pos_int_continue   2027   4   7   %oparray_pop   showpage   showpage   1890   3   9   %oparray_pop   showpage   showpage
D [18/Sep/2020:14:38:20 -0400] [Job 3] Dictionary stack:
D [18/Sep/2020:14:38:20 -0400] [Job 3] --dict:972/1684(ro)(G)--   --dict:1/20(G)--   --dict:83/200(L)--   --dict:83/200(L)--   --dict:133/256(ro)(G)--   --dict:310/450(ro)(G)--   --dict:33/64(L)--   --dict:6/9(L)--   --dict:12/20(L)--
D [18/Sep/2020:14:38:20 -0400] [Job 3] Current allocation mode is local
[b]D [18/Sep/2020:14:38:20 -0400] [Job 3] Last OS error: Broken pipe
D [18/Sep/2020:14:38:20 -0400] [Job 3] GPL Ghostscript 9.25: Unrecoverable error, exit code 1[/b]
D [18/Sep/2020:14:38:20 -0400] [Job 3] Rendering completed
D [18/Sep/2020:14:38:20 -0400] [Job 3] PID 21300 (/usr/lib/cups/filter/gstoraster) stopped with status 1.
D [18/Sep/2020:14:38:20 -0400] [Job 3] End of messages

[rcrsn51]

If BionicPup32 works over USB, then it should also work to a remote printer. Sending the print job to a remote printer should NOT generate a filter error. Does CUPS offer any other connection protocols, like socket:?

A 32bit driver in a 64bit environment is ABSOLUTELY not going to work, unless you have some kind of 32bit support in play.

The BionicPup64 problem is definitely Ghostscript. There are two possibilities - BionicPup64 has a different and incompatible version than BionicPup32, or the 32bit compatibility system is not working correctly.

[vtpup]

Thanks rcrsn51. That helps to understand what's happening better. To go further:

1.) Can you give a suggestion for how to determine whether BP64 ghostscript is the problem, or the 32 bit compatibility sfs is?

2.) Knowing now that the driver does work in 32 bit with USB, can you give a suggestion where to look if network printing does work with Tahrpup32, but not with Bionicpup32?

The address used for both is

ipp://192.168.1.1/printers/Dell

. I have also tried

http://192.168.1.1:631/printers/Dell

with equivalent results.

[rcrsn51]

If you run the CUPS Add Printer procedure, how does it discover the remote printer? Just with the ipp: protocol?

Does socket://192.168.1.1 work too?

[vtpup]

The ipp protocol discovery doesn't work. In fact no network discovery worked IIRC with CUPS 2.x. The addresses were entered manually.

I'll try socket, but I have to reboot out of this test pup and re-load BP32 and tahr32 to compare. Will report when finished.

[vtpup]

Socket 192.168.1.1 and socket 192.168.1.1:9100 do not work on Tahrpup32 or Bionicpup32. The 9100 port is not open on 192.168.1.1, as tested by Peasyport. But 631 is. I checked the manual for the modem's print server and it says it wants the following format:
"http://192.168.1.1:631/printers/printername" That works in Tahrpup32. But it throws the "Filter Failed" CUPS error in Bionicpup32.

Tahr32 uses CUPS 1.4.8, and Bionic32 uses CUPS 2.2.7. Both Tahr and Bionic print properly via USB, so the printer driver is not the problem. I would guess also because USB printing works, that for Bionic32, Ghostscript also is not the problem. So why is Bionic32 throwing that message when I try a network connection instead of USB?

Note: all of the above were tested with fresh CD OS instances using pfix=ram, and with the firewall off.

[rcrsn51]

The ipp protocol discovery doesn't work. In fact no network discovery worked IIRC with CUPS 2.x. The addresses were entered manually.

I checked this in BIonicpup32. The CUPS Add Printer dialog discovered two networked printers easily. However, some networked printers don't advertise their presence to CUPS, so a manual install in required. The simplest protocol is socket:.

[vtpup]

Okay, got it. See my reply above yours for additional info.

[rcrsn51]

OK. Here is what I think is happening. In recent versions of CUPS, the role of the ipp protocol has expanded to handle things like AirPrint. CUPS requires extra components that BionicPup may not have. Or the ipp print server on your router is no longer compatible with this setup.

[vtpup]

Hi rcrsn51 I'm using http print protocol now, not ipp, per the manual, though they both work for Tahr32.

Is it possible to use an earlier version of CUPS in Bionicpups, or is that unworkable or a difficult job to convert to?

(btw Bionicpup64 is what I ultimately want to use, not BionicPup32, but for now I'm using the 32 bit version for isolating the problem)

[mikewalsh]

@vtpup :-

I'm going to bow out, now that rcrsn51 is assisting you with this. If anybody can help you get this working, it'll be Bill; he practically wrote the book on printing under Puppy. I'm a complete noob compared to him.....and I'll be the first to admit it, too.

CUPS, Ghostscript, drivers, etc.....it's like so much Greek as far as I'm concerned. I have drivers that work for me with my Epson printer/scanner, and that's good enough for me. Not much point my getting underfoot when I can't really make any worthwhile contributions..!

The only reason I tracked down that 32-bit libcups was because I, too, came across several forum posts on other fora where various people had had the same issue; Xerox insisting the 32-bit package was designed to run in 64-bit distros, providing you had a number of 32-bit components installed. It sounded a bit odd, but I've come across stranger....maybe it IS supposed to work that way. Who knows?

(*shrug*)

Good luck with it, anyway.


Mike.

[rcrsn51]

Hi rcrsn51 I'm using http print protocol now, not ipp, per the manual, though they both work for Tahr32.

Look in /usr/lib/cups/backend. You may find that http is just a symlink to ipp.

Is it possible to use an earlier version of CUPS in Bionicpups, or is that unworkable or a difficult job to convert to?

You could try going into the Tahrpup repo and getting its CUPS package. Also its Ghostscript. But I have no experience with this.

(btw Bionicpup64 is what I ultimately want to use, not BionicPup32, but for now I'm using the 32 bit version for isolating the problem)

I don't know enough about the BionicPup 32bit compatibility pack to comment on this.

[vtpup]

@vtpup :-
I'm going to bow out, now that rcrsn51 is assisting you with this.
Mike.

Thanks Mike for helping, this is one of those giant pains, that finally just wastes everyone's time. I've spent a couple days now trying to get a networked printer that has been working fine for years now on Tahrpup working with BionicPup and as usual when dealing with CUPS get entirely bogged down in its idiosyncracies, when all I want to do is just print and forget it. It's not like i expect CUPS to provide 3D CAD or a rocket's satellite guidance system. Just send a single darn file to a printer.

So, I don't blame you, I'm going to give up, too. It's been two solid days of trying to track down solutions, testing fresh installs, poring over error messages, etc. It's just not worth it. Bionicpup64 may have lots of advantages, but I can't do without a printer on a day-to-day working system, and I don't want to spend days more trying to guess at what an older version of CUPS needs in a 64 bit system, or whether there's a problem with the 32 bit compatibility sfs, or ghostscript, or ipp.

Time to think about something more productive.

Thank you again, all who responded, and apologies for this rabbit hole.

[rcrsn51]

I can think of only one work-around to this situation. Set up a dedicated Tahrpup32 machine with the printer connected by USB. Enable CUPS Port 631 sharing.

Then any client computer could send a job to this print server using the CUPS Raw format. The client could be 32/64bit and would not need the printer driver.

[mikewalsh]

@rcrsn51 :-

Bill, this is somewhat of a stab in the dark, I know, but.....what about the p910ND print server? Would it be of any use in this situation? If you recall, I found it helped back when I was using one of the Bionic RC versions....7.9.4, I think it was. Just a thought...

EDIT:- No, scratch that idea; I remember now why I ended up using it. The drivers installed fine with Eppi, and the printer itself installed successfully....but for some reason, at least for me, the CUPS sharing function was not behaving itself. That was how I came to be running the p910ND server....


Mike.

[vtpup]

A hardware workaround shouldn't be necessary. The fact that recent 32 bit CUPS can't handle a proven working 32 bit driver over a network is a deficiency. Or built-in obsolescence.

64 bit CUPS should also be backward compatible for 32 bit drivers. It may well be, under the Puppy workaround of a 32 bit compatibility SFS, but the fact that even 32 bit CUPS fails to network with a 32 bit driver means zero chance.

[rcrsn51]

Are you sure that the problem is with CUPS itself or with Bionic's implementation of CUPS?

As a test, I would try Fatdog64, which has a full CUPS and a 32bit compatibility system.

[vtpup]

Nope, not sure of that, frankly because I don't know much about CUPS under the hood. It's a continuingly feature-changed monster utility, with files and folders scattered all over the OS, which has provided more frustration over a dozen years for me than any other aspect of Linux. Whether that was due to actual CUPS code, or some dependency I can't personally distinguish. I can say it seems like at least some of the shortcomings are likely in it's code, and also likely in its dependency strategies. For instance, printing even stopped working yesterday on a couple of our Tahrpup32 machines in the house. What the? Why? And why not all of them??? As if to answer that, eventually it was all of them, as I tried to test them. Now this had happened before inexplicably, and we'd tried workarounds. Sometimes the system seemed to cure itself.

Eventually yesterday, after all the Bionicpup testing, I figured out that Tahr CUPS 1.4.8 (which I'd been using for years) "Modify Printer" wizard did not properly modify printers, period. Even if settings were entered correctly. However trusting that function meant I couldn't test or solve anything by trying alternate settings. Eventually I found that by deleting printers and then completely re-installing them printing was restored.

Is "modify printer" a function of CUPS code? Is it that of a dependency? I dunno. All I know is, it is typical of my experiences with versions of CUPS over the years. I cannot think of another piece of software I've run on Linux that is to me so likely to give odd results, setup issues, and is so recalcitrant toward my solving those problems. My biggest fear whenever I upgrade Puppy isn't the functionality of programs or the OS. It's dread of some new version of CUPS. I have dread of CUPS! In fact, I seem stuck now, at the end of the Puppy line because of (choose one) CUPS or its dependencies or both. Because this conglomeration with all it's newest bells and whistles and security improvemnents can't handle simply sending the same file via network that it can via USB.

[tosim]

           Install Driver for Dell c1760 Color Laser
http://askubuntu.com/questions/513943/h ... ith-ubuntu
If you have a 64-bit system, copy and paste this into  Terminal
          sudo apt-get install libcupsimage2:i386
     If you have a 32-bit system, ignore that terminal command and proceed.
 Download the Ubuntu .deb drivers from Xerox for their Phaser 6000 model. It comes packaged in a .zip file:
https://www.support.xerox.com/support/p ... ived=false
(The Dell C1760nw is a "repackaged" version of this model, which means that the core printing device works the same as a Xerox Phaser 6000 because it came from the same factory, but it is assembled and sold to retailers by Dell instead of Xerox.)
 You will need to save this .zip file, and extract its contents with a right-click if you are looking at it in the File Manager. A folder will be extracted, and therein will be a .deb package file. You should double-click this to open it.
 You may encounter a window saying that the package is of "bad quality". You can safely ignore this; it's coming up because of an incorrectly entered variable that declares the creator of the file.
 Then, install the printer. If you are prompted to choose a printer manufacturer and model, enter it as a Xerox 6000b. It works!
 Note that all of these steps are still required to use the printer over the network.
               ***Above worked great for me.***
install(all three) libcups2 in Synaptik
https://forums.linuxmint.com/viewtopic.php?t=152946
http://en.community.dell.com/support-fo ... t/19525015
http://codefucius.blogspot.com/2014/03/ ... er-up.html
http://linuxibos.blogspot.com/2012/05/s ... linux.html

[rcrsn51]

@tosim: If you read the entire thread, you will see that these Ubuntu users are installing a 32bit compatibility environment.

Are you reporting that this technique also works in Puppy?

[rcrsn51]

All I know is, it is typical of my experiences with versions of CUPS over the years. I cannot think of another piece of software I've run on Linux that is to me so likely to give odd results, setup issues, and is so recalcitrant toward my solving those problems

Maybe that's because Puppy has not implemented CUPS as it would be in a mainstream Linux.

I am currently using CUPS 2.2.10 in the Starter Kit and it is rock-solid.

[mikewalsh]

@vtpup:-

Just as an aside - bearing in mind your own description of CUPS 'oddities' over the years! - I too have had to follow some slightly unorthodox procedures at times.

I'm a long-standing fan of Epsons; never bothered trying anything else, 'cos they're so amazingly reliable. A bit on the agricultural side perhaps - to some - but they just keep chugging away, year after year... Most only get "binned" when the waste ink pad gets full, and after a preset number of runs a message is triggered that declares you must take it to an Epson service centre, to have X, Y and Z done to it.....it basically quits working until you do. At this point, it's cheaper to buy a new model....

Anyway; Epson provide .deb packages - once you've got past their customer service people all declaring loudly,"We don't DO Linux drivers..!!" Which is odd, given that

a) Their Linux stuff was all developed for them by their Japanese 'sister' company, Avasys (who had a bang-on reputation for their code before selling-out to Epson), and
b) They were one of the original founding members of the Linux Foundation..!

The .debs have always installed flawlessly. However; in 32-bit Pups, I've always had to install the printer firstly with a generic Epson 'Escp-r' .pet package Bill produced, followed by 'modifying' to the correct specific driver after that.

For the 64-bitzers, I've had far better luck using the 'Eppi' command-line installer package Bill put together. If I click-installed the .deb driver packages directly, CUPS could never, EVER "see" the printer.....


Mike.

[vtpup]

           Install Driver for Dell c1760 Color Laser
http://askubuntu.com/questions/513943/h ... ith-ubuntu
If you have a 64-bit system, copy and paste this into  Terminal
          sudo apt-get install libcupsimage2:i386
     If you have a 32-bit system, ignore that terminal command and proceed.
 Download the Ubuntu .deb drivers from Xerox for their Phaser 6000 model. It comes packaged in a .zip file:
https://www.support.xerox.com/support/p ... ived=false
(The Dell C1760nw is a "repackaged" version of this model, which means that the core printing device works the same as a Xerox Phaser 6000 because it came from the same factory, but it is assembled and sold to retailers by Dell instead of Xerox.)
 You will need to save this .zip file, and extract its contents with a right-click if you are looking at it in the File Manager. A folder will be extracted, and therein will be a .deb package file. You should double-click this to open it.
 You may encounter a window saying that the package is of "bad quality". You can safely ignore this; it's coming up because of an incorrectly entered variable that declares the creator of the file.
 Then, install the printer. If you are prompted to choose a printer manufacturer and model, enter it as a Xerox 6000b. It works!
 Note that all of these steps are still required to use the printer over the network.
               ***Above worked great for me.***
install(all three) libcups2 in Synaptik
https://forums.linuxmint.com/viewtopic.php?t=152946
http://en.community.dell.com/support-fo ... t/19525015
http://codefucius.blogspot.com/2014/03/ ... er-up.html
http://linuxibos.blogspot.com/2012/05/s ... linux.html

Tosim, I realize you are only trying to help, but you don't seem to have read my second post in this thread, where all of this was already tried. This attempt at a solution assumes we don't have a working driver (we do). and we are trying to get it working on a 64 bit system (we aren't, for present test purposes.

To clarify the issue, taking rcrsn51's suggestion, we tested on a 32 bit system: (Bionic32) using that driver, and tried printing via USB. Everything worked.

Then using the exact same setup, merely switched from USB to a netaddress of http://192.168.1.1:631/printers/Dell and got the "Filter Failed" message. The netaddress above is absolutely correct, as verified by the print server manual, and also verified in an existing 32 bit puppy system, Tahrpup32. Where printing has been working with that driver and that address in CUPS 1.4.8 for years.

rcrsn51 (and my) conclusion is that the newer CUPS 2.2.7 system in BionicPup32 is broken in this regard, either in its code (a program or dependency bug), or its setup and implementation in Bionicpup32 (an OS bug). Something is clearly wrong.

CUPs should print, given a working driver, proven via USB, and a correct network address.

It doesn't

[rcrsn51]

@vtpup: Did you ever try the driver on Bionic64 with the compatibility pack on USB?

[vtpup]

rcrsn51 do you mean the 32 bit compatibility sfs? or is there something else? I will if that's what you mean....

Also, I really think it's in networking, though, going back to Bionic32.

Do you think it could be a ipv6 vs ipv4 problem? Something simple like that?

[vtpup]

E [17/Sep/2020:08:48:16 -0400] Unable to open listen socket for address [v1.::1]:631 - Address family not supported by protocol.

[rcrsn51]

Connect the printer by USB.
Run BIonic64
Load the Bionic 32bit compatibility pack (I got it from Quickpet).
Install and test the printer.

I did a simulated test of this setup and the driver worked.

[bigpup]

I have not read all posts, so this may have been done.

Bionicpup64 8.0 has some updates and bug fixes.
Run Quickpet->Info->Bionicpup updates
Save and Reboot so changes are now being used.

[rcrsn51]

@vtpup: If you can get the driver working in Bionic64, then here is your best long-term solution.

Get a little Ethernet-USB print server box. Plug it into a free Ethernet port. Connect the printer by USB. The box should provide the more friendly socket protocol instead of the troublesome ipp.

If CUPS cannot auto-detect the server, scan your LAN with PeasyPort for Port 9100. Install the printer manually in CUPS.

[rcrsn51]

@vtpup: I own an Ethernet-USB print server. I connected it to my LAN and plugged in an Epson printer.

I ran Bionic64 and installed the Epson driver.

I ran PeasyPort and located the server.

I ran CUPS and manually installed the printer using ipp. The server queue is called LP1, so the URI was

Code: Select all

ipp://192.168.2.39:631/LP1

This worked correctly. So Bionic64 is capable of handling the ipp protocol.