Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The printer jams and you have to shut it off to clear it.
Before I turn the printer on again you kill the active print job with lprm.
I turn the printer back on and it immediately starts printing garbage and spitting out paper.
Cycling the power to the printer doesn't help (you shut the printer off once already).
I can stop the printer by killing the parallel port process, but after that nothing will print. Rebooting doesn't help. The only way to get printing back is to remove the print queue and build a new one.
This seems like a major piece of dumbness in CUPS - or maybe I'm the dumb one. It seems to me that lprm should be able to kill the active print job, including getting rid of whatever is in the parallel port buffer.
By the way, a Google search on this subject found other reports of this problem but no acceptable solution. The closest anyone came was a Perl script that kills the parallel port process, but in my case that makes the queue permanently non-functional.
Have you tried unplugging your printer and letting it sit for 15-20 minutes to allow the capacitors providing power to the data buffer to fully discharge? That usually works for me.
Edit:
It's the printer's internal data buffer that's the problem, not the spooling buffer in your box.
Thanks for the suggestion. No, the printer memory isn't the problem, it's the parallel port buffer. That's demonstrated by the fact that killing the parallel port process immediately stops the printer.
Hmmm. You're right, sorry. I thought I had already learned to read the whole thread before I reached a conclusion; apparently I hadn't. There SHOULD be some way of flushing the buffer without killing the whole process.
Yea, it seems like this should be totally transparent to the user. lprm should flush the buffer when it kills the active print job. As it is, it's a trap waiting to be sprung whenever the printer screws up during a print job.
Maybe I'm just missing something obvious, but this seems like one of those little things that really turns off people to Linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.