Start Chatting. Thanks for chatting with us. Ask me anything. Save Transcript. Chat started at 4. Confirm End Chat Continue to Chat. Close Chat Save Transcript. Chat Ended. This site uses cookies to provide an improved digital experience. You can learn more about the cookies we use as well as how you can change your cookie settings by clicking here. By continuing to use this site without changing your settings, you are agreeing to our use of cookies. This only needs to be entered once to user current Configuration File.
Learn more. How to show the CUPS printer jobs history? Ask Question. Asked 7 years, 9 months ago. Active 9 months ago. Viewed 87k times. Improve this question. Santiago Santiago 1 1 gold badge 3 3 silver badges 12 12 bronze badges. Of course I have no access to the printer right now, and therefore I cannot check if the file was printed or not. Via the web interface it is easy. What is that, could you explain a bit more?
Add a comment. Active Oldest Votes. Improve this answer. HalosGhost 4, 10 10 gold badges 31 31 silver badges 40 40 bronze badges. This will only show the completed for your userid. You can give a list of users like this: lpstat -W completed -u user1,user2.
Does lpstat have a rolling window for the completed print job history, or does it show all jobs that were ever completed? Community Bot 1. I'm not sure where the web interface gets its information from. Faheem Mitha Faheem Mitha In that case, the printer would almost certainly offer the IPP-over-USB protocol if it has been manufactured after mid Debian 11 bullseye is geared up to auto-setup network and USB print queues with cups-browsed.
Should auto-set fail and debugging cups-browsed is an unattactive proposition or there is a more complex situation to resolve, a manual queue setup with lpadmin , the CUPS web interface or system-config-printer is recommended.
Driverless printing for CUPS and cups-filters is here to stay. While it will be sone time before CUPS 3. The Concept of Driverless Printing Driverless printing is targeted at the client side of printing and refers to the ability of the client device computer, smartphone, tablet, laptop etc to print without having to install any static capability files or drivers manufacturer-specific or otherwise on the client.
There exist a variety of methods for a client to submit a job to a printing system and print driverlessly: Print directly from an application on the client. Send the job as an email attachment to a special address. Web print. The document is uploaded from a web browser via a web form style interface. This page is intended to highlight and explain driverless printing in the context of directly communicating with a printer using packages provided by Debian, so not all these methods will receive attention here.
Furthermore, details for using iOS and Android mobile clients are not treated. Remember that CUPS can act as a client or server. However, the focus here is on CUPS as a client connecting to a printer that offers driverless printing functions.
Driverless Printing and Printers A traditional printing system based on CUPS, cups-filters and cups-browsed generally obtains information about printer features and capabilities from what is stored in a static capability file such as a PostScript Printer Description PPD file. This static file is stored on the client device desktop computer, laptop, tablet etc itself. If the PPD on the client requires the sending of a job using a non-standardised Page Description Language PDL , a driver would be required for converting to the printer-specific PDL and that driver too would have to be on the client.
A client that regularly connected to different printers would have to maintain static capability files and drivers for each printer. This is not seen as an acceptable situation, especially for mobile clients, which may have limited storage for PPDs and drivers and that may lack resources, such as battery power.
Neither is it deemed particularly realistic for a user to have to set up or reconfigure a laptop computer or mobile device for each printer that is encountered. This requires a level of expertise and a time and effort commitment that cannot be assumed to be possessed. Then contrast the printer situation with the behaviour of other peripherals like keyboards, mice, cameras and USB mass storage.
Plug such devices in and they are immediately and reliably there to be used. The objective is to have printing no less available when a printer is detected. This is the discovery protocol; accessible printers can be identified and selected from the Bonjour broadcasts of the printer. The discovery protocol is also configured to obtain capability information from accessible printers to include in its broadcasts. The client and printer communicate using the IPP protocol.
This is the transport protocol; it can obtain capability information from the selected printer and transport data to it. There is a common PDL that the client can send and that the printer will accept. The common PDL is based on what is obtained from the capability information for the selected printer. Note again that we are talking here about sending a job directly to a printer, not to a print queue being advertised by CUPS.
In the case of PWG raster the raster format was chosen because it is a simpler format than that of the high-level languages, which also require significant resources on the printer. Streaming was chosen to send a job to a printer rather than generating a file that is downloaded and then printed. This way large jobs don't take up too much memory or storage space on the printer and printing commences with minimum delay. Apple raster has existed for a number of years and is used with Apple's AirPrint.
Unfortunately, it is not officially documented but it is known that it and PWG raster are very similar. It is based on CUPS raster and is well-documented. The file produced by the filter is sent directly to the printer with IPP, so no vendor-specific filters are involved. This opens up the possibility of avoiding the use of non-free drivers on the CUPS client or server used for printing. The print job is submitted to the printer with the data produced from the filters.
In addition, applications using the dialog always produce a PDF to send to the printer. If this is not an acceptable PDL for the printer, printing will not take place. It is kept in sync with the original by incorporating any changes to the original. The cups-filters PPD generator is used by default with cups-browsed when a local print queue is auto-created for an IPP network printer. The original PPD generator requires all printer capability, option, and choice information from the printer attributes IPP request.
The cups-filters generator can, in some cases, fall back to using information from the Bonjour record or even hard-coded default values. This adds support for some legacy printers. It is mandated by the Wi-Fi Direct standard. Since version 1. Printers have bugs in their implementation of IPP. The ENVY has also been discovered from the printer's Bonjour broadcasts using the dnssd and ipp backends. The device-uri for the printer can also be found with the ippfind or driverless utilities.
A list of printer capabilities is returned and a PPD is automatically generated by CUPS for use by command line programs and applications. This is the method employed when CUPS sets up a temporary queue on a client. Open the web interface and choose Administration.
0コメント