Differences between revisions 68 and 69
Revision 68 as of 2021-05-06 15:47:52
Size: 43433
Editor: Brian Potkin
Comment: Added a link to an ipp-usb bug report.
Revision 69 as of 2021-06-10 10:26:31
Size: 43519
Editor: Brian Potkin
Comment: Link to a useful post regarding the driverless utility. 4520 is 4502.
Deletions are marked like this. Additions are marked like this.
Line 177: Line 177:
`ippfind` locates DNS-SD advertised printers and queues.
`driverless` (a cups-filters utility) lists IPP printers only.
`ippfind` locates DNS-SD advertised printers and queues. `driverless` (a cups-filters utility) lists [[https://lists.linuxfoundation.org/pipermail/printing-architecture/2021/004048.html|IPP printers only]].
Line 483: Line 482:
For an HP Envy 4520: For an HP Envy 4502:

Translation(s): none


Driverless printing with CUPS. Requires at least CUPS 2.2.2 and version 1.13.0 of cups-filters. Debian 10 (buster) and later installations meet both these conditions. The advice here (an ethernet or wireless connection) and here (a USB connection) could get your modern IPP printer going with little effort.

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:

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. In its server capacity it can emulate an IPP Everywhere or Apple AirPrint printer. 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.

The response of printer manufacturers to the desire for driverless printing has been to enhance their printers in the following way:

  • The printer advertises its presence and capabilities with mDNS/DNS-SD (Bonjour). 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. A driverless-enabled printer will offer at least one of Apple raster, PWG raster, PDF or PCLm as a PDL.

Note again that we are talking here about sending a job directly to a printer, not to a print queue being advertised by CUPS.

PDLs for Driverless Printing

Two raster formats, Apple raster and PWG raster, have been developed to implement driverless printing.

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. Printer-embedded PostScript interpreters can be buggy and/or slow and PostScript also has the disadvantage that it makes interoperability between client and printer difficult because PostScript does not fit cleanly with the IPP and PWG models. 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. The MIME media type is image/urf.

  • PWG raster is a more recent raster format, devised to be used with IPP Everywhere printers. It is based on CUPS raster and is well-documented. The MIME media type is image/pwg-raster.

CUPS: PWG and Apple Raster

The abilitity to create Apple raster files has been added to the existing PWG raster support in CUPS and made its appearance in CUPS 2.2.2; this enhancement was soon applied in version 1.13.0 of cups-filters and cups-browsed. Complete support for IPP Everywhere printers was already in Debian, so, with CUPS 2.2.2, AirPrint printers joined the class of printers that will work driverless with Debian.

With the incorporation of the two raster formats as a PDL in CUPS, IPP 2.0 to allow for querying the capabilities information from the printer and Bonjour/DNS-SD to find the printers in the network, Debian has everything needed for driverless printing to an IPP printer.

The processing of a job to create an Apple raster file is taken care of by CUPS' rastertopwg filter. 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 CUPS PPD Generator

To support driverless printing fully, CUPS has a PPD generator that will drive a traditional CUPS print queue. The generator queries the printer and creates the necessary PPD options and values needed to support Apple Raster, PWG Raster, JPEG, and PDF printing. A CUPS generated PPD uses the everywhere model and can be identified from the *PCFileName "ippeve.ppd" line in the PPD.

  • A non-GTK application calls on CUPS to determine the filters required to convert the print file to a printer supported PDL.

  • The auto-generated PPD is consulted and a printer-ready file in the required PDL is produced.
  • The print job is submitted to the printer with the data produced from the filters.
  • If a PDF or JPEG file is being printed, it can be sent to the printer without any filtering; this is accounted for in the *cupsFilter2 lines that are added to the generated PPD.
  • A text file sent to an AirPrint or IPP Everywhere printer would often be filtered by CUPS and cups-filters to output an Apple or PWG raster file. If the printer has PDL support for MIME media type application/pdf, a PDF would be sent instead because a PDF is given the highest priority. Typical possibilities for the filter chain are:

                                     ->|--------------------------------------------> Printer
text -> texttopdf -> pdftopdf -> PDF ->| gstoraster -> rastertopwg -> PWG raster ---> Printer
                                     ->| gstoraster -> rastertopwg -> Apple raster -> Printer
  • The GTK print dialog does not use CUPS to communicate directly with IPP printers. 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.

The cups-filters PPD Generator

This generator uses the driverless utility and is basically a copy of the PPD generator from CUPS that has been put into the libcupsfilters library. It is kept in sync with the original by incorporating any changes to the original. A libcupsfilters generated PPD can be identified from the *PCFileName "drvless.ppd" line in the PPD.

Although the cups-filters PPD generator is kept closely in step with the CUPS one, the two are not identical:

  • The original PPD generator only supports PWG Raster, Apple Raster, PDF, and JPEG as printer PDLs. The cups-filters PPD generator also accepts (with lower priority) PostScript, PCL-XL, and PCL 5c/e for legacy printers.

  • 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.

  • The cups-filters PPD generator is more flexible when it comes to adding support for PDLs. For example, consider PCLm: PCLm has nothing to do with PCL 5c/e and PCL-XL but is a streaming PDF-based, raster protocol (Printer Control Lanaguage-Mobile). It is mandated by the Wi-Fi Direct standard. Since version 1.17.0 of cups-filters, application/PCLm has been a supported MIME media type via the rastertopclm filter. CUPS itself will never support PCLm.

text -> texttopdf -> pdftopdf -> PDF -> gstoraster -> rastertopclm -> PCLm ---> Printer
  • cups-filters has a policy of supporting new driverless printing technologies (see above), so its PPD generator is quite likely to accomodate developments.
  • Printers have bugs in their implementation of IPP. It is more likely that the cups-filters PPD generator will produce a fix than the CUPS version of the generator.

Creating a Driverless Print Queue with lpadmin (Short Version)

Obtain the URI of a printer:

driverless

Set up the print queue (uses the CUPS PPD generator):

lpadmin -p <print_queue_name> -v <URI> -E -m everywhere

Set up the print queue (uses the cups-filters PPD generator):

lpadmin -p <print_queue_name> -v <URI> -E -m driverless:<URI>

Creating a Driverless Print Queue with lpadmin

Some familiarity with a device-uri is assumed in this section.

With a single AirPrint printer on the network a partial output from /usr/sbin/lpinfo -v could be:

network dnssd://HP%20ENVY%204500%20series%20%5BFAFAC2%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-308d99fafac2
network socket://192.168.7.235:9100
network ipp://envy4500.local:631/ipp/print

The snmp backend has found the printer will accept jobs on port 9100 (socket://192...). CUPS will not set up an everywhere queue using this URI because it is unable to query the printer with it.

The ENVY 4500 has also been discovered from the printer's Bonjour broadcasts using the dnssd and ipp backends. Both these URIs are equally stable and can be used for driverless printing, with a dnssd URI being preferred if the ipp URI is using a numeric IP address.

The device-uri for the printer can also be found with the ippfind or driverless utilities. ippfind locates DNS-SD advertised printers and queues. driverless (a cups-filters utility) lists IPP printers only.

ippfind                         (Shows IPP printers and print queues).
ippfind -T 5                    (Possibly more reliable).
ippfind ! --txt printer-type    (Show IPP printers only).

driverless                  (To get the device-uri).
driverless list             (For the device-uri and printer metadata).
driverless <device-uri>     (Generate a PPD for the printer at <device-uri>).

A queue for driverless printing from a client is now set up with

lpadmin -p <print_queue_name> -v <device-uri> -E -m everywhere

The everywhere model causes the printer referred to by the -v option to be queried. A list of printer capabilities is returned and a PPD is automatically generated by CUPS for use by command line programs and applications.

It may be preferred to have the PPD generated by cups-filters, so first find the driver URI (driverless:ipp://...) with

driverless list

and create the queue with

lpadmin -p <print_queue_name> -v <device-uri> -E -m <driver URI>

If the -v option is the URI of a queue on a remote CUPS server, this technique can create a driverless queue on the client for a remote non-raw queue. This is the method employed when CUPS sets up a temporary queue on a client.

Creating a Driverless Print Queue with the CUPS Web Interface

Some familiarity with the CUPS web interface is assumed in this section.

  • Open the web interface and choose Administration. Select Add Printer.

  • Your printer will be under the Discovered network Printers:, probably with more than one entry. Choose the entry that contains the word driverless and move on to Continue.

  • Check that Connection is ipp://... and continue to the next page.

  • Under Model there should be options of IPP Everywhere and driverless, cups-filters. The first option uses the CUPS PPD generator and the second the cups-filters PPD generator. Select and activate Add Printer.

Creating a Driverless Print Queue with system-config-printer

Some familiarity with system-config-printer is assumed in this section.

  • Start system-config-printer and choose Add followed by Network Printer.

  • Highlight the printer entry and choose the Driverless IPP entry.

  • Moving on has system-config-printer searching for a driver, auto-generating a PPD with the cups-filters generator and offering a screen to describe the printer. Choose Apply when done.

  • system-config-printer cannot use the CUPS PPD generator.

Creating a Driverless Print Queue with cups-browsed (Short Version)

Edit /etc/cups/cups-browsed.conf to uncomment the directive below:

CreateIPPPrinterQueues All

Restart cups-browsed:

systemctl restart cups-browsed

cups-browsed version 1.27.1 changed the default for CreateIPPPrinterQueues to All. Considering that cups-browsed is a recommended package for cups-daemon, this change should lead to making IPP printers immediately visible and available on a bullseye installation.

Creating a Driverless Print Queue with cups-browsed

This method leads to discovery of an AirPrint or IPP Everywhere printer and the automatic set up of a print queue with lpadmin. A PPD for the queue is created using the cups-filters PPD generator. The CUPS PPD generator may be used instead; see the UseCUPSGeneratedPPDs directive in the cups-browsed.conf manual. The PPD is used to display printer options for command line programs and in applications. There are just two operations a user has to carry out:

  • Edit /etc/cups/cups-browsed.conf to set the CreateIPPPrinterQueues to All or Driverless and restart cups-browsed.

CreateIPPPrinterQueues All
CreateIPPPrinterQueues Driverless

systemctl restart cups-browsed

cups-browsed version 1.27.1 changed the default for CreateIPPPrinterQueues to All. Considering that cups-browsed is a recommended package for cups-daemon, this change should lead to making IPP printers immediately visible and available on a bullseye installation.

  • Check the existence of the queue and its options with

lpstat -t
lpoptions -p <queue_name> -l
  • The device-uri should begin ipp://.... The queue name is got from lpstat -t.

  • The queue persists provided the printer is switched on and cups-browsed is running.
  • With the CreateIPPPrinterQueues directive cups-browsed sets up a queue for a remote printer. With NewIPPPrinterQueuesShared Yes in /etc/cups/cups-browsed uncommented the printer is shared with other machines on the local network.

  • cups-browsed supports also a kind of legacy driverless printing. This means that some other common PDLs such as PostScript, PCL-XL, and PCL 5c/e are supported and also older IPP versions (1.x). Note that missing capability information can be replaced with default values and that implementations of these languages in the printers are often not reliable, so that, in contrast to official driverless printing, printing often does not work perfectly. Note that the PCL of HP inkjets does not work and therefore cups-browsed does not auto-create queues for this PDL.

IPP-over-USB: The Basics

The previous methods to set up driverless printing with CUPS are presented in the context of a network-only connection (wireless or ethernet). They require the Internet Printing Protocol (IPP) for querying the capabilities of the printer so that the PPD can be generated. They also need IPP to send option settings to the printer (as IPP attributes).

Fortunately, driverless printing is not confined to the network only but also works in exactly the same way via USB using the IPP-over-USB daemon, ipp-usb. ipp-usb serves for using the device via USB; this is fully independent of whether there is also a network connection available between the computer and the printer. A recent AirPrint printer should support IPP-over-USB. The support situation regarding USB-only IPP printers has yet to be completely clarified, but it is known that such devices are not guaranteed to understand the protocol.

The IPP USB specification describes an extension to USB that defines a standard for making IPP available over a USB Print class interface, and is intended to allow USB connected devices to achieve functional parity with network connected devices using IPP. In other words, whatever can be done over a network connection may also be done over a USB connection. A USB connected printer is therefore seen as a network printer when IPP-over-USB is used.

The previous sentence indicates that users employing the CUPS web interface or system-config-printer should be looking under network printers to establish a connection with the printer.See SystemPrinting for more detail.

It should be straightforward and reliable to use a printer or multi-function device via ethernet or WiFi and, in general, this is the recommended type of connection to employ. Also, such network connections allow easy sharing of the device. Some reasons why a user may want or have a preference for a USB connected MFD or printer are:

  • A local network does not exist and Wi-Fi Direct is not offered by the device.

  • The local network is regarded as operating unreliably.
  • The computer is USB-only.
  • The MFD or printer is USB-only.
  • The user sees setting up a network connection as an extra complication to avoid.
  • The MFD or printer is rarely used. When it is, it is simpler and easier just to plug it into a USB port.
  • The user values having a USB connection as a fallback method for printing.
  • Sending confidential documents via USB is mandated as being more secure than sending them over a network.

Whether a printer can use IPP-over-USB may be determined by executing lsusb -v|less and searching for the lines containing bInterfaceClass.*7. A bInterfaceProtocol line should be found a few lines below each bInterfaceClass line.

Alternatively, execute

lsusb -v | grep -A 3 bInterfaceClass.*7

A value of 4 for bInterfaceProtocol indicates a USB IPP device.

IPP-over-USB: Automatic Discovery and Setup

Beginning with version 2.3.3-2 the cups-daemon package installs ipp-usb as a recommended package. When an IPP-over-USB device is connected to the computer, systemd will use /lib/systemd/system/ipp-usb.service to start the daemon. cups-browsed is also installed by default, so, because the USB connected printer emulates a network printer, it will auto-create a driverless print queue for the printer.

  • The result is that the USB connected printer becomes immediately available for printing to. Nothing else need be done. Manually setting up a driverless print queue is also an option.

Note that IPP-over-USB reserves the USB interface connection with the printer/scanner exclusively for itself and communication with a printer/scanner device by software that does not operate using the IPP-over-USB protocol becomes impossible while ipp-usb is running. This is a consequence of the design of USB communication. It is not a bug in ipp-usb.

  • For example, a print queue for an HP MFD can be set up with a vendor driver and PPD, but printing to it will not take place because the software does not use the IPP-over-USB protocol. The same holds true for all other drivers, free or non-free. Only driverless print queues will work with IPP-over-USB. It would be as well to remove existing queues based on vendor drivers to avoid the appearance of non-working queues in print dialogs. Removing vendor packages (free or non-free) from the system is also something to consider.

Communicating with a USB connected scanner via classic SANE backends such as libsane-hpaio, sane-pixma or sane-epson2 also becomes impossible with the ipp-usb daemon active and running.

  • Expecting the non-free Brother and Samsung backends to work would also be unreasonable. Only driverless backends will work with IPP-over-USB. A good solution to have reliable scanning with IPP is to install the independent SANE backend, sane-airscan, in addition to the official SANE backend,sane-escl, that comes with libsane1. sane-airscan is a highly regarded backend that interworks with IPP-over-USB very well. A non-working SANE backend may be made invisible to a frontend by commenting out the appropriate entry in /etc/sane.d/dll.conf or /etc/sane.d/dll.d.

An important idea underlying IPP-over-USB is having the ability to expose the local USB-connected printer only to localhost and not to the entire local network. This condition is fulfilled by using at least version 0.8-1 of avahi-daemon.

  • If it is desired to share the printer on the local network or with iOS and Android devices, alter the interface parameter in /etc/ipp-usb/ipp-usb.conf to all.

IPP-over-USB: Investigation and Troubleshooting

Remember, although the actual physical connection is a USB one, the device has effectively become a networked device advertised on localhost by default, not to the local network. All the usual network commands may be used in addition to the CUPS commands.

  • Determine the state of ipp-usb:

systemctl list-units "ipp-usb*" | grep service
systemctl status ipp-usb

  • A portion of a typical output from avahi-browse -rt _ipp._tcp is shown below. Note that the DNS-SD advertisment is on localhost. The port used is not 631 because this is claimed by cups-daemon. ipp-usb takes the printer's DNS-SD name (usually configurable via the printer's web interface and often known as the Bonjour name), adds a space followed by (USB) as a suffix to it and uses the resulting string for announcing the printer. The port number is incremented when additional printers are attached to the USB bus. avahi-browse is in the avahi-utils package.

=     lo IPv4 ENVY4500 (USB)  Internet Printer        local
hostname = [desktop.local]
address = [127.0.0.1]
port = [60000]
  • Access the printer's EWS for administrative tasks via a browser:

http://127.0.0.1:60000
http://desktop.local:60000

  • If cups-browsed is not on the system or it hasn't generated a print queue, not even after re-plugging the printer, a user has the option of creating a driverless print queue using the CUPS web interface, system-config-printer or lpadmin. But keep in mind that the IPP-over-USB printer is seen as a network device and be sure always to look under network printers with both of these setup solutions. Ignore the temptation to set up a local USB connection even though the device is on USB. Under the model/driver entries look for entries containing driverless or IPP Everywhere.

  • Obtain a URI for the printer by executing:

driverless

lpadmin -p <chosen_printer_name> -v <URI> -m everywhere
lpadmin -p <chosen_printer_name> -v <URI> -m driverless:<URI>
  • lpstat -l -e shows all available destinations on the local network. ENVY4500_USB_ is the queue name or destination created by CUPS for an IPP-over-USB printer. It is formed from what ipp-usb sees as the printer's DNS-SD name. ENVY4500 (USB). ipp://ENVY4500... is the URI of the printer. Having permanent instead of network indicates a destination that has been auto-setup by cups-browsed or installed with lpadmin, the CUPS web interface or system-config-printer.

ENVY4500_USB_ network none ipp://ENVY4500%20(USB)._ipp._tcp.local/
envy4500usb permanent ipp://localhost/printers/envy4500usb ipp://ENVY4500%20(USB)._ipp._tcp.local/
  • List the printer or print queue specific options and their current settings. These options should also be presented in the print dialog of an application:

lpoptions -p <destination> -l

  • USB print queues previously set up with vendor drivers (HP, Brother, Canon, Samsung etc) will amost certainly cease to work, so they become candidates for deletion. In fact, a user could consider removing the vendor software completely as it doesn't provide any useful function unless it is intended to switch between IPP-over-USB and vendor drivers.

CUPS 2.2.4 and Driverless Printing

CUPS' ability directly to browse the DNS-SD (Bonjour) broadcasts of remote print queues and printers, previously absent, was introduced in CUPS 2.2.4. This means that a system with CUPS 2.2.4 or later, such as Debian 10 (Buster), will display remote queues and IPP printers with lpstat -e and in the print dialogs of some applications without cups-browsed, needed on Debian 8 (Jessie) and Debian 9 (stretch) for remote queue management, being on the system. No action on the part of the user is required.

Essentially, CUPS uses its CupsGetDests and CupsEnumDests functions to discover shared queues and IPP printers on the local network that can be printed to and makes them available for display in an application. Whether or not the application displays them depends on the chosen application. Printing to an enumerated entry leads to the formation of a temporary queue. A temporary queue is intended to last for a minute only.

  • lpstat -a shows only queues of the local CUPS daemon and not DNS-SD advertised queues or printers. lpstat -e and lpstat -l -e additionally enumerate queues and printers that can be accessed on the network.

  • The Qt print dialog of applications like okular and qpdfview enumerates remote, shared queues and printers and uses a temporary queue for printing.

  • The libreoffice print dialog behaves the same way as the Qt dialog.

  • the GTK print dialog has its own way of dealing with a network printer. Unfortunately, applications that print through this dialog do not make use of CUPS' temporary queue formation. To have a queue for an IPP printer visible and usable, users should manually set up a queue with lpadmin, the CUPS web interface or system-config-printer or rely on cups-browsed to do it for them,

CUPS 2.2.4 and the GTK Print Dialog

The print dialog of GTK applications such as firefox and evince does not function in the same way as the Qt and Libreoffice dialogs. It obtains queue and printer information directly from DNS-SD broadcasts and not through CUPS, so it has no knowledge of what CUPS 2.2.4 and later are capable of doing. Basically, except for local queues, CUPS is unneeded. It may as well not be on the system.

In addition, using the GTK print dialog always results in the production of a PDF. Printers that that do not have PDF as an acceptable PDL will not process such a print job.

This leads to the following problem.

  • Although the GTK dialog is aware of IPP printers on the local network via DNS-SD, it does not support printing to them and will possibly display a destination print and Rejecting Jobs for an IPP printer.

  • One solution is to check that cups-browsed is on the system and, in cups-browsed.conf, have cups-browsed create permanent, local queues for remote queues and printers (rather than the CUPS temporary queues that Qt applications and LibreOffice use). This technique is described above.

  • Because the GTK dialog may already show local queues and remote queues on CUPS servers it is likely that, with this first solution, only the additional entry for the remote printer is wanted. So alter cups-browsed.conf to have

CreateRemoteCUPSPrinterQueues No

Managing queues and printers in the GTK dialog with the first solution also leads to the other dialogs adopting cups-browsed as the queue and printer management application.

Duplicate Print Queues

The entries shown in the print dialogs of applications are the names of existing or potential print queues. The existing queues have been set up manually or automatically with cups-browsed. A potential queue is an on demand queue. The existing queues may also be enumerated with lpstat -a. Additional entries from lpstat -e are potential queues.

It can happen that a user observes that the print dialog contains two entries with slightly different names for the same physical printer. The two entries are often referred to as duplicate entries or duplicate printers. The user expects to see only one list entry and confusion may result from being unsure which entry should be selected from the dialog list.

  • The default behaviour of the printing system is to install a queue for a network or USB connected printer with cups-browsed. For unknwown reasons, but possibly due to habit, the user proceeds to install a queue manually for the same printer. This results in a duplicate entry in the print dialog. It is a user-induced duplication and revealed from the output of lpstat -a. The solution is to let the printing system do its job and remove the manual queue or not install it in the first place.

  • A second cause of duplicate entries occurs when the GTK print dialog is used with the default printing system. The DNS-SD broadcasts of any remote print server or IPP printer are directly browsed to produce a dialog entry. cups-browsed browses the same DNS-SD broadcasts and also populates the dialog, leading to duplicate entries. CUPS is not involved in producing the GTK dialog entry, so the solution awaits the efforts of GTK developers.

  • In normal circumstances an on demand, temporary queue entry should not appear as a duplicate entry because cups-browsed takes over the entry and creates a local queue with it. Okular and LibreOffice show this behaviour. Without cups-browsed and with a manual queue, a duplicate is possible. The solution is to give the manual queue the same name and device URI as the potential queue displays in lpstat -l -e. CUPS will then use the permanent, manual queue.

  • It is possible to use IPP-over-USB and have an ethernet or wireless connection to the printer at the the same time. There will be two entries in a print dialog. The solution is obvious!

CUPS and Driverless Printing: Miscellaneous

  • AirPrint and IPP Everywhere printers generally have a web interface for administration. For an ethernet or wireless connected printer it is accessed in a web browser with

http://<IP_address or hostname of the printer>

For a USB connected printer using ipp-usb the URL is

http://localhost:60000

The hostname can be obtained from the output of avahi-browse (see below). Make sure that IPP support and Bonjour broadcasting on the printer are enabled. The configuration options will probably be accessed under a Networking link and it could be that activating AirPrint is sufficient to activate both services.

avahi-browse -rt _ipp._tcp

Bonjour-advertised IPP printers are now identified. Look for entries beginning URF=... and pdl=... . If URF=... exists and pdl=... contains image/urf you have an AirPrint printer.

For an HP Envy 4502:

URF=CP1,MT1-2-8-9-10-11,OB9,OFU0,PQ3-4-5,RS300-600,SRGB24,W8-16,DEVW8-16,DEVRGB24-48,ADOBERGB24-48,DM3,IS1,V1.3
pdl=application/vnd.hp-PCL,image/jpeg,application/PCLm,image/urf

For a Brother MFC-J650DW:

URF = SRGB24,W8,CP1,IS1,MT1-8-11,OB9,PQ4-5,RS300,OFU0,V1.2,DM3
pdl = application/octet-stream,application/vnd.brother-hbp,image/pwg-raster,image/urf,image/jpeg

The pdl entry for the MFC-J650DW contains an additional image/pwg-raster. This printer will accept and print PWG raster files. It could be an IPP Everywhere printer, but that all depends on whether it fulfills all the criteria necessary for the manufacturer to self-certify it with the Printer Working Group (PWG). However, the presence of image/urf indicates the printer IPP implementation is sufficient for driverless printing to be used with CUPS.

  • Driverless printing usually allows only adjustments on printing as they are thought out by the printer manufacturers. A printer driver like Gutenprint allows a lot fine tuning that goes far beyond a manufacturer's possibilities. This driver may suit photo enthusiasts more than a driverless solution. Having said that, the quality of text or images printed with rastertopwg is yet to be challenged.

  • Purchasing a printer with Apple raster and/or PWG raster capability means looking at the box containing the printer and printer brochures and manuals. AirPrint has been going for some time so it is usually fairly prominent as a feature in the literature. IPP Everywhere is much newer and may not be adertised.

Summary

interface = all

Acknowledgements

Didier 'OdyX' Raboud <odyx@debian.org> for guiding and supporting CUPS 2.2.2, cups-filters and cups-browsed through the experimental archive and into unstable; also for packaging ipp-usb and sane-airscan; Till Kamppeter <till.kamppeter@gmail.com> for his integration of cups-filters and cups-browsed with CUPS 2.2.2; also for producing a patch to allow IPP-over-USB to work on localhost with Avahi and encouraging Trent Lloyd <trent.lloyd@canonical.com> to apply it. Michael R. Sweet <msweet@apple.com> for developing the rastertopwg filter to support Apple raster. Alexander Pevzner <pzz@apevzner.com> for the creation of ipp-usb and sane-airscan.

See Also


CategoryPermalink | CategoryPrinter