My network printer (HP Laserjet 5M) suddenly won't print. For instance, I can try to print from the command line `lpr postscriptfile.ps', the command passes OK, the local CUPS web page says the job completes, but there is no printout. However, an official CUPS test page prints fine. All this used to work a few days ago, and I don't think I've changed much of anything.

To further confound me, another network printer (HP Laserjet 4050) works fine! I can print postscript files and test pages to it, just as I normally would.

Any tips on how to troubleshoot this weird problem?

no tips here!

but thanks for your post, i can now print to my samba HP4050N printer, using your great lpr command all my configuration without converting it to gedit.

Well, that was an unintended consequence. And to think, lpr is practically deprecated after 30 (?) years of loyal service. I guess it'll never die.

Anyway, the problem is weird. When I print from certain applications (I think those trying to use KDE print) the printer will respond, warm up, and then just not print. If I use lpr or other applications (which are probably just using lpr anyway, like Mozilla firefox) there is no response at all. The local CUPS web page says that every job is completed, though.

I guess I have a solution.

I think something was screwed up with the generic postscript driver/PPD file. I could see a few errors in my CUPS error_log file, after I turned debug mode on. Anyway, I used system-config-printer to change to the HPIJS driver, which lets me print. The quality seems a bit worse, but its still perfectly usable unless you pick nits.

I don't know what happened to the postcript PPD file (if that was it). I might have yum update'd a new cups a little while ago. I took me a while to notice the problem.

If anyone didn't know, the site www.linuxprinting.org has excellent stuff. Check the tutorials in the sidebar.

In my case update with CUPS was the problem. Once installation of an update finishes it asks you to choose between two config files, an old and a new config. You may want to check wich config file you are using. I am not sure if this will actually help, or just waste your time