Waiting for printer to finish message when selecting printer

Running LEAP 42.1 with KDE desktop and using mainly HP printers connected over lan.
I can now print from all printers but one printer, a LaserJet 5M, has the captioned message alongside in the printer selection window.
If I select this printer it prints but the message is always there. What causes this message and how may I remove it?
Budgie2

Hmmm… does restarting CUPS fix this message issue?

sudo systemctl restart cups

Maybe arising from an earlier communication issue with the printer? The following command should report the same

lpstat -p

Report back with complete output

You should also be able to restore via the CUPS web configuration interface

http://localhost:631/printers/

Hi Deano

Will look at this also as an alternative to yast.

I confess I am overwhelmed by printing stuff. I used to be happy setting up printers with yast but then found I needed hplip and hp-setup to get the best out of colour printer. I now have HP logo in my system tray which is next to useless as I have to go to yast to reactivate printer if it goes inactive on its own, a small printer icon appears when I print and somewhere along the line KDE gets involved too.

Rant over. Many thanks for the help. All seems OK now.

Ok, so restarting CUPS did the trick. Very good.

I only ever use the CUPS web interface for configuring/managing printers, and YaST provides an openSUSE-specific utility for doing the same. That said, HPLIP provides its own configuration utilities (CLI and GUI), so it makes sense to use them for configuring at least, but it is still possible to do via CUPS web interface or CLI manually if you know what you’re doing. At the end of the day, they are all essentially adding/modifying a configuration to /etc/cups/printers.conf, and the appropriate ppd file to /etc/cups/ppd/ directory.

So do you just keep restarting CUPS every time you see this? What is causing this to happen?

Are you referring to the OP’s problem with non-responsive network-attached HP printer? I guess sometimes there are communication problems which causes CUPS to flag them as such. Further debugging would be needed to know more details about the nature of such an issue, (and perhaps a bug report).