Version: (using KDE KDE 3.5.4) Installed from: Slackware Packages Compiler: GCC 3.4 OS: Linux The situation like below: I started printing (60 pages from KPDF if it matters), all data has been sent to the printer and job was removed from queue. Unfortunately the paper ran out after 58th page. I loaded paper but my printer (LJ HP1018) doesn't have any button to continue printing. KDE didn't show any window (like Windows does) so I wasn't able to continue.
KDEPrint can't do anything to alleviate that problem. Once the job is sent off by KDEPrint, it is handled by CUPS. And CUPS can't do much either (at the present time): once CUPS has sent the jobfile off, it is handled by the printer (which may store it on its local disk until the job is completed). Most modern printers do handle conditions like "paper out" all by themselves (and auto-continue printing once the paper is filled up again). Some printers do have the capability to communicate in a bi-di way with their print client. Often times this bi-di communication is using a proprietary protocol, and the vendors have given only their Windows drivers the possibility to react on "paper out" conditions. A future version of CUPS will offer some of the capabilities direct bi-di chatter with the printer via its network backends (based on standard protocols such as SNMP). This one can't be fixed by KDEPrint.
I forgot: I propose you get in touch with the HP Linux printer driver developers via their website http://hplip.sf.net/ and ask them for advice and about their development roadmap.
Closing old Resolved status bug.