CUPS
Related articles
CUPS is the standards-based, open source printing system developed by Apple Inc. for OS X® and other UNIX®-like operating systems.
Contents
Installation
Install the cups, ghostscript, and gsfonts packages.
If the system is connected to a networked printer using the Samba protocol, or if the system is to be a print server for Windows clients, also install the samba package.
If you intend to "print" into a PDF document, also install the cups-pdf package. By default, pdf files are stored in /var/spool/cups-pdf/$USER
. The location can be changed in /etc/cups/cups-pdf.conf
.
Start and enable org.cups.cupsd.service
. Optionally, CUPS can use Avahi browsing to discover unknown shared printers in your network. This can be useful in large setups where the server is unknown. To use this feature, start cups-browsed.service
.
Printers
Detecting the printer
USB
To see if your USB printer is detected:
lsusb
(...) Bus 001 Device 007: ID 03f0:1004 Hewlett-Packard DeskJet 970c/970cse
Parallel port
To use a parallel port printer, the lp
, parport
and parport_pc
kernel modules are required.
dmesg | grep -i print
parport0: Printer, Hewlett-Packard HP LaserJet 2100 Series lp0: using parport0 (polling)
If you are using a USB to parallel port adapter, add the printer using a different connection type and then change DeviceID in /etc/cups/printers.conf
:
DeviceID = parallel:/dev/usb/lp0
Local Network
Newer versions of cups tend to be good at detecting printers, and tend to pick the right hostname, but unless you have added the host to your /etc/hosts will fail to resolve for normal printer activities. Unless you want to make your printer ip static, avahi-daemon can help autoresolve your printer hostname. Install and start Avahi then restart cups:
systemctl restart org.cups.cupsd.service
You can avahi-discover find the name of your printer and its address (ex. Address: BRN30055C6B4C7A.local/10.10.0.155:631) or just add .local to the hostname cups was using (ex. BRN30055C6B4C7A.local). Double check that everything is working with ping:
ping XXXXXX.local
should work, if it doesn't go back and make sure that avahi is running and that you have the right hostname. After this, make sure that the hostname in the cups web interface is the .local hostname.
Installing the best driver
CUPS already includes a few printer drivers. In that case you can just select it in the list and your printer will likely work.
If there is no driver for your printer included with CUPS, there might be a PPD available at the OpenPrinting Printer List. Select the brand and type/model of the printer to find out what driver the site recommends. Download the PPD file from the site. When the CUPS web interface asks for a printer driver/PPD, select "Or Provide a PPD File: Choose file".
The website will also suggest a driver. For instance, for the HP LaserJet 5P, the site recommends the ljet4
driver. It is possible that this driver is already included with CUPS, otherwise you will need to install it. If so, you can try out Foomatic or Gutenprint, or else find the driver in CUPS/Printer-specific problems.
- Foomatic
foomatic-db, foomatic-db-engine and foomatic-db-nonfree are database-driven systems for integrating free software printer drivers with common spoolers under Unix.
- Gutenprint
The gutenprint drivers are high-quality, open source printer drivers for various Canon, Epson, HP, Lexmark, Sony, Olympus and PCL printers supporting CUPS. They also support ghostscript, The GIMP, and other applications.
- Manufacturer-specific drivers
A lot of printer manufacturers supply their own Linux drivers. Many are available in the official repositories or in the AUR. See CUPS/Printer-specific problems for a list of drivers.
Configuration
The CUPS server configuration located in /etc/cups/cupsd.conf
. After editing, restart org.cups.cupsd.service
to apply any changes. The default configuration is sufficient for most users.
Groups with printer administration privileges are defined in SystemGroup
in the /etc/cups/cups-files.conf
. The sys
group is used by default.
Local printers
To have the printer installed on the system, fire up a browser and point it to http://localhost:631. The CUPS web interface should be displayed from which all administrative tasks can be performed.
Go to Administration and enter the root login and password information your GNU/Linux system. Then, when the administrative interface has been reached, click on Add Printer. A new screen will be displayed allowing the following information to be entered:
- The spooler name, a short but descriptive name used on the system to identify the printer. This name should not contain spaces or any special characters. For instance, for the HP LaserJet 5P could be titled
hpljet5p
. - The location, a description where the printer is physically located (for instance "bedroom", or "in the kitchen right next to the dish washer", etc.). This is to aid in maintaining several printers.
- The description should contain a full description of the printer. A common use is the full printer name (like "HP LaserJet 5P").
The next screen requests the device the printer listens to. The choice of several devices will be presented. The next table covers a few possible devices, but the list is not exhaustive.
Device | Description |
---|---|
AppSocket/HP JetDirect | This special device allows for network printers to be accessible through a HP JetDirect socket. Only specific printers include support for this option. |
Internet Printing Protocol (IPP or HTTP) | Used reach the remote printer through the IPP protocol either directly (IPP) or through HTTP. |
LPD/LPR Host or Printer | Select this option if the printer is remote and attached to a LPD/LPR server. |
Parallel Port #1 | Select when the printer is locally attached to a parallel port (LPT). When the printer is automatically detected its name will be appended to the device. |
USB Printer #1 | Select when the printer is locally attached to a USB port. The printer name should automatically be appended to the device name. |
If installing a remote printer, the URL to the printer will be queried:
- An LPD printer server requires a
lpd://hostname/queue
syntax. - An HP JetDirect printer requires a
socket://hostname
syntax. - An IPP printer requires a
ipp://hostname/printers/printername
orhttp://hostname:631/printers/printername
syntax.
Next, select the printer manufacturer in the adjoining screen along with the model type and number in the subsequent screen. For many printers multiple drivers will be available. Select one now or search on OpenPrinting Printer List for a good driver. Drivers are easily able to be changed later.
Once the driver is selected, CUPS will inform that the printer has been added successfully to the system. Navigate to the printer management page on the administration interface and select Configure Printer to change the printer's settings (resolution, page format, ...).
Test the printer
To verify if the printer is working correctly, go to the printer administration page, select the printer and click on Print Test Page.
If the printer does not seem to work correctly, click on Modify Printer to reconfigure the printer. The same screens as during the first installation will appear but the defaults will now be the current configuration.
If the printer does not function, clues may be found by looking at the CUPS error log located at /var/log/cups/error_log
. In the next example a permission error is discovered, probably due to a wrong Allow setting in the /etc/cups/cupsd.conf
file.
tail /var/log/cups/error_log (...) E [11/Jun/2005:10:23:28 +0200] [Job 102] Unable to get printer status (client-error-forbidden)!
Remote printers
Local CUPS server
Remote print servers can be accessed by adding an IPP "printer" to the local CUPS server, with a URI of ipp://192.168.0.101:631/printers/<name-of-printer>
.
See CUPS/Printer sharing#Between GNU/Linux systems for details on setting up the remote print server.
Without a local CUPS server
Install libcups, and set up Avahi's .local hostname resolution, otherwise the client will fail to print with an "Unable to locate printer" error. See Avahi#Hostname resolution for details.
There are currently two methods for accessing a remote print server.
The first method involves setting CUPS_SERVER
for each application, for instance for Firefox:
# (Substitute printserver.mydomain with your print server name) CUPS_SERVER=printserver.mydomain:port firefox
The second method involves editing /etc/cups/client.conf
and setting the ServerName
directive:
/etc/cups/client.conf
# (Substitute printserver.mydomain with your print server name) ServerName printserver.mydomain
The remote system's default printer setting will be used by default.
Printer sharing
See CUPS/Printer sharing.
Remote administration
If remote administration is needed, then access to the CUPS administration will need to be granted from more systems than the localhost. Add the allowed hosts to the <Location /admin>
block in /etc/cups/cupsd.conf
, using the same syntax as described in CUPS/Printer sharing#Manual setup. Note that three levels of access can be granted:
<Location /> #access to the server <Location /admin> #access to the admin pages <Location /admin/conf> #access to configuration files
To give remote hosts access to one of these levels, add an Allow
statement to that level's section. An Allow
statement can take one or more of the forms listed below:
Allow from all Allow from host.domain.com Allow from *.domain.com Allow from ip-address Allow from ip-address/netmask Allow from @LOCAL
Deny statements can also be used. For example, if wanting to give full access to all hosts on your local network interfaces, file /etc/cups/cupsd.conf
would include this:
# Restrict access to the server... # By default only localhost connections are possible <Location /> Order allow,deny Allow from @LOCAL </Location> # Restrict access to the admin pages... <Location /admin> Order allow,deny Allow from @LOCAL </Location> # Restrict access to configuration files... <Location /admin/conf> AuthType Basic Require user @SYSTEM Order allow,deny Allow from @LOCAL </Location>
You might also need to add:
DefaultEncryption Never
This should avoid the error: 426 - Upgrade Required when using the CUPS web interface from a remote machine.
- print-manager — A tool for managing print jobs and printers (KDE).
- system-config-printer — A CUPS printer configuration tool and status applet (GNOME and others)
- gtklp — GTK+ interface to CUPS.
If your user does not have sufficient privileges to administer the cups scheduler, system-config-printer will request the root password when it starts. To give users administrative privileges without needing root access, see #Configuration.
Usage
CUPS can be fully controlled from command-line with nice tools, i.e. the lp* and the cups* command families. Here follows a crash-course. See CUPS local documentation for more tips on command-line tools.
On Arch Linux, most commands support auto-completion with common shells. Also note that command-line switches cannot be grouped.
- List the devices
# lpinfo -v
- List the drivers
# lpinfo -m
- Add a new printer
# lpadmin -p printer -E -v device -P ppd
The printer is up to you. The device can be retrieved from the 'lpinfo -v' command. Example:
# lpadmin -p HP_DESKJET_940C -E -v "usb://HP/DESKJET%20940C?serial=CN16E6C364BH" -P /usr/share/ppd/HP/hp-deskjet_940c.ppd.gz
In the following, the printer references the name you have used here to set up the printer.
- Make the printer use the raw driver
# lpadmin -p printer -m raw
- Set the default printer
$ lpoptions -d printer
- Check the status
$ lpstat -s $ lpstat -p printer
- Deactivate a printer
# cupsdisable printer
- Activate a printer
# cupsenable printer
- Remove a printer
First set it to reject all incoming entries:
# cupsreject printer
Then disable it.
# cupsdisable printer
Finally remove it.
# lpadmin -x printer
- Print a file
$ lpr file $ lpr -# 17 file # print the file 17 times $ echo "Hello, world!" | lpr -p # print the result of a command. The -p switch adds a header.
- Check the printing queue
$ lpq $ lpq -a # on all printers
- Clear the printing queue
# lprm # remove last entry only # lprm - # remove all entries
Troubleshooting
See CUPS/Troubleshooting.