Sorted it thanks.

I 'upgraded' to a 14.2 install, by getting a root terminal in the Slackware64/ directory of the install cd and running 'upgradepkg --reinstall *.txz' in each subdir that mattered. Firefox is back to 45.2.0, but I can gingerly take up some later packages if needed. I had tried to upgrade to current but it wasn't clean. The printer now showed in Libreoffice, but I got the 'filter failed' error from cups. That was sorted in an xterm as follows hp-setup is in the hplip package. Then I had to resume the printer. I think it's only that my printer seems to be a right royal bitch to install that gave me such grief.

1 members found this post helpful.

Thanks for that. I could not see my HP Laserjet Pro in Libreoffice or Okular but could print via hplip. Hp-setup cured problem for me as well. Am running Slackware64 current.

cool.
also some time ago get in that problem, printers in libreoffice was gone.
slackware64-current.
today install latest libreoffice from AlienBob.
the same - "print to file" and "generic printer".
in cups all is ok.
i have two printers - one network printer, and another -local, hp 1320, usb one.
delete 1320 in cups, then add it - no changes for libreoffice.
delete ./config/libreoffice - again no any luck.
try hp-setup - also no luck... :-O
do anyone also have that problem, a printers is gone in libreoffice, but work in cups and all other apps?

Have you tried hp-setup?

I have the same problem. More, some older windows software being run by wine (current) also lack proper printer recognition.
Cups sees my HP_LaserJet_Professional_P_1102w properly just like HPLIP.
I use 32-bit current SW.

Does HPLIP throw any errors?

I tried an update to current and landed myself in brown smelly stuff: /var/log/packages missing files, but the actual package was there; packages gone but not replaced in an "Upgrade." Packages not upgraded; version conflicts all over the place. Probably the Bermuda Triangle intersected with the Twilight Zone over my house when I was doing it. I was beating my head off the wall; and bleating for help for a while. People seemed to react with 'wtf?' or 'smh' but I eventually sorted it.

looks like, it was my last slackware in "current" incarnation.
broken things on almost every step.
how good, at home i have macos, who "just works"...

From my experience, it seemed like 'current' in 32 or 64 bit isn't a good distro right at the moment. In particular, mesa-17.x causes issues for a whole rake of stuff, and then some current versions barf without a later mesa than 11.x. I managed to have firefox, perl, python, gcc and everything dependent on them all bellyaching. Some things are being advanced silently by simply copying the old package into a new directory in Alien's packages, for example minidlna. The libs now conflict and a compile from source is best. I take it as a sign they're busy men.

I'm sure they'll get there, but they're not there yet.

1 members found this post helpful.