Hello, a "mee too" mail ;-)
On Aug 9 13:55 Aaron wrote: > I'll also note this. However to continue you should only need to press the > paper button on the front of the printer (or okay depending on the model) > and it should continue printing. I will enter this has a possible > enhancement as well however. ... > On 8/9/07, Dmitry P <[EMAIL PROTECTED]> wrote: > ... > > When paper is out, printer stops working; power indicator on the front > > panel blinks and nothing happens. > > How can I force my HP DJ 3650 to continue printing further after I've > > added a paper? I have a HP DeskJet 3325 and usually it doesn't start to print when I try to use it after a longer time. It happens even when there is paper loaded (and fully inserted into the tray) and I see a message like "paper out" in the "lpstat" output (I don't remember the exact message). Then the one single button on the front of the printer blinks but regardless if I press it once short or for a longer time, it doesn't start to print. What helps is to switch off the printer (i.e. disconnect it from the power supply), cancel the current active job, switch on the printer and re-submit the job. I don't use this weak printer model often - only for some tests (e.g. when there is a new HPLIP version) and therefore I guess it might happen only after a longer time when it was not used or perhaps when the computer was rebooted or whatever else obscure condition which let this problem happen. > > In this situation in Windows appears an information window > > with the buttons "Continue printing" and > > "Cancel printing"; it would be convenient > > to display such window in Linux too. It cannot be implemeted in the printing system. But it can of course be implemented in a user application like hp-toolbox (or whatever else user application to watch the state of the print queues) and as far as I know hp-toolbox does already automated refresh of the device status. Reason: 1. To pop up a dialog box on the user's desktop, non-user processes (e.g. the daemon cupsd and/or filters and/or backends) would need permission to access the user's desktop. By default non-user processes do not have such permissions. By default non-user processes should not have such permissions. 2. The printing system operates queue based. This means that a submitted job may have to wait for a longer time in the queue until it becomes actually processed. At this time the user may already be logged off from his desktop. Therefore push information to the user is not done and cannot be done because it would be pure luck if it works. 3. It would cause many complicated additional issues when printing via network (i.e. the HPIJS driver runs on a drifferent machine than the user's desktop). In contrast the user can poll information at any time from the printing system (e.g. call "lpstat" or "kjobviewer" or the CUPS web interface or "hp-toolbox" and so on). This solves the above issues because the user can start a polling program on his desktop which queries the printing system on whatever host. I.e. there is no need to think about how to push information to the user. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ HPLIP-Help mailing list HPLIP-Help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hplip-help
