Then you cannot remove the "to be printed" documents and have to kill the spool service...thats a problem since Win2K..shame on you Microsoft PUUUUUUU!
Ffs Microsoft get your shit together, windows may be dead to you but there a over a million running systems that you bought your way into. So sit up straight in your chair and get through that decade long backlog...
Like Booo but more firmly ;)
And the very best part: on Fedora 32 or better, scanning Just Works! This is the result of a project to implement both Microsoft's and Apple's scanning protocols in SANE, and somehow the result seems substantially better than Apple or Microsoft's implementations.
On Linux you're way less lucky if you wanna print, god forbid the document is more complex than a text file.
Regardless of using PCL6 or the Lexmark driver from Lexmark, the printer continues to be unable to print PDFs directly from the browser. Other PDF viewers print normally. CUPS logs no error but prints it on a piece of paper instead.
When attempting to view the print queue of my printer, it crashes if a document is being sent but has not started pritning yet. It is fine if the document is queued but not printing.
Sometimes, CUPS doesn't print the document immediately but waits 30 minutes. Other documents sent to the queue in the mean time print immediately. Sometimes the program that attempts to print causes a hard lockup in CUPS, so I have to restart the CUPS service.
"Connect printer" isn't the easiest in CUPS if it decides that autodiscovery doesn't do it, which it often does.
My favorite one is how a guy in my office one day was not able to print. Well he could print, but only from applications that used the really, really old Windows printing API. So basically you could print from Notepad, and that was it.
We tried everything to get printing to work, but could not figure out the problem. This led to a wipe and reload of the OS. After I got it reloaded, I tested out printing, and it worked great. Success!
Next day, he comes in and is again not able to print. Turns out that the problem was due to the drivers from his personal HP printer at home. The printer was auto-detected, and Windows automatically downloaded the new driver for that printer. That somehow fucked up the entire printing subsystem again so no printers would work at all.
Isn't Internet Printing Protocol pretty much that, and supported by most printers?
Kind of like Microsoft's brand new "Universal Print" is a brand name applied to the Internet Printing Protocol, although it uses Active Directory for discovery.
Google, recently announced they were killing CloudPrint to support IPP instead.
It's too bad there doesn't seem to be much industry support for a common, open driver system. PS was a good try but seems Adobe licenses killed that one. Similar with PCL and HP. There was a glimmer of hope with XPS years ago but that quickly fizzled.