Laserjet 1300 fails to print with hplip-3.18.7

I have an HP Laserjet 1300 printer, which uses the hpcups PCL3 filter from slackware64-current's hplip-3.18.7-x86_64-2.txz. The filter fails to work in that version. When a print job is run, it reports:

hpcups[24329]: segfault at 4da000 ip 00007f9c173f48e5 sp 00007ffdec1d0b90 error 6 in libImageProcessor-x86_64.so

If I revert to hplip-3.18.6 it works fine.

Edit Stack trace:

Stack trace of thread 24329: #0 0x00007f9c173f48e5 n/a (libImageProcessor.so) #1 0x00007f9c16fec77b imageProcessorProcessLine (libImageProcessor.so) #2 0x00000000004066cb n/a (hpcups) #3 0x0000000000406e07 n/a (hpcups) #4 0x00007f9c15d6eba7 __libc_start_main (libc.so.6) #5 0x000000000040404a n/a (hpcups)

when I looked at this at first I thought there was just an issue relative to an improper installation of the binary blob

https://www.linuxquestions.org/quest...ml#post5887721

but looking at how the linked bug evolved maybe the best option is to use the debian patch (in place of the one I prepared) and remove this closed source libImageProcessor for good

https://bugs.launchpad.net/hplip/+bug/1785230

https://sources.debian.org/src/hplip...-is-clo.patch/

can you have a look as I haven't at hand an hp printer to test this?

Originally Posted by ponce when I looked at this at first I thought there was just an issue relative to an improper installation of the binary blob https://www.linuxquestions.org/quest...ml#post5887721 but looking at how the linked bug evolved maybe the best option is to use the debian patch (in place of the one I prepared) and remove this closed source libImageProcessor for good https://bugs.launchpad.net/hplip/+bug/1785230 https://sources.debian.org/src/hplip...-is-clo.patch/ can you have a look as I haven't at hand an hp printer to test this?

If I apply the debian patch to hplip-3.18.7 then the segfault goes away.

However, presumably something is missed by not linking to the binary blob. Do you have any idea what?

Also, as I say, hplip-3.18.6 works OK with the binary blob, so presumably hplip-3.18.7 must have tickled something the wrong way.

Originally Posted by chrisVV However, presumably something is missed by not linking to the binary blob. Do you have any idea what?

Ah, having now read up more about it, I see that the binary blob is new in hplip-3.18.7. It seems to be fundamentally broken, at least as far as slackware is concerned. Presumably it has been linked by HP against something which is ABI incompatible with something in slackware.

Originally Posted by chrisVV If I apply the debian patch to hplip-3.18.7 then the segfault goes away. However, presumably something is missed by not linking to the binary blob. Do you have any idea what?

I think this is clarified by the latest post in the bug report

https://bugs.launchpad.net/hplip/+bu...230/comments/6