Cups General

cmd:cups, Cupsys

Help

Support

Cups Forums http://www.cups.org/newsgroups.php

cups packages

cups in debian etch, using packages from sid

aptitude -t unstable install foomatic-db-engine foomatic-db-gutenprint foomatic-filters
aptitude -t unstable install cupsys cupsys-bsd cupsys-driver-gutenprint gutenprint-doc

% aptitude -t unstable install foomatic-db-engine foomatic-db-gutenprint foomatic-filters
The following NEW packages will be installed:
  foomatic-db foomatic-db-engine foomatic-db-gutenprint foomatic-filters
  ijsgutenprint libijs-0.35
The following packages will be upgraded:
  libxml2
The following packages are RECOMMENDED but will NOT be installed:
  cupsys-client lpr lprng rlpr
1 packages upgraded, 6 newly installed, 0 to remove.
Need to get 3315kB/4084kB of archives. After unpacking 56.6MB will be used.
The following packages have unmet dependencies:
  libxml2-dev: Depends: libxml2 (= 2.6.26.dfsg-3) but 2.6.27.dfsg-1 is to be installed.
Resolving dependencies...
The following actions will resolve these dependencies:
Upgrade the following packages:
libxml2-dev [2.6.26.dfsg-3 (now) -> 2.6.27.dfsg-1 (testing, unstable)]
Score is 0
The following packages will be upgraded:
  libxml2 libxml2-dev

% aptitude -t unstable install cupsys cupsys-bsd cupsys-driver-gutenprint gutenprint-doc
The following NEW packages will be installed:
  cupsys cupsys-bsd cupsys-client cupsys-common cupsys-driver-gutenprint
The following packages will be upgraded:
  gutenprint-doc libdbus-1-3
2 packages upgraded, 5 newly installed, 0 to remove.
Need to get 4722kB of archives. After unpacking 12.9MB will be used.

cupsys_1.2.6-1
cupsys-bsd_1.2.6-1
cupsys-client_1.2.6-1
cupsys-common_1.2.6-1
cupsys-driver-gutenprint_5.0.0-3
foomatic-db_20061031-1
foomatic-db-engine_3.0.2-20061031-1
foomatic-db-gutenprint_5.0.0-3
foomatic-filters_3.0.2-20061031-1
gs-esp_8.15.3.dfsg.1-1
libcupsys2_1.2.5-1

AOK!!!

documented on: 2006.11.13

cups in debian etch, using gutenprint

aptitude install foomatic-db-engine foomatic-db-gutenprint foomatic-filters
aptitude install gs-esp
aptitude install cupsys cupsys-bsd cupsys-driver-gutenprint gutenprint-doc

aptitude install escputil

% aptitude --purge-unused purge foomatic-db-engine foomatic-db-gutenprint foomatic-filters cupsys cupsys-bsd cupsys-driver-gutenprint cupsys-driver-gimpprint foomatic-db-gimp-print

% aptitude install foomatic-db-engine foomatic-db-gutenprint foomatic-filters
The following NEW packages will be installed:
  foomatic-db foomatic-db-engine foomatic-db-gutenprint foomatic-filters
  ijsgutenprint libijs-0.35
The following packages are RECOMMENDED but will NOT be installed:
  cupsys-client lpr lprng rlpr
Need to get 0B/3314kB of archives. After unpacking 56.3MB will be used.

% aptitude install cupsys cupsys-bsd cupsys-driver-gutenprint gutenprint-doc
The following NEW packages will be installed:
  cupsys cupsys-bsd cupsys-client cupsys-common cupsys-driver-gutenprint
  gutenprint-doc
0 packages upgraded, 6 newly installed, 0 to remove and 784 not upgraded.
Need to get 987kB/4459kB of archives. After unpacking 14.0MB will be used.

cups in debian sarge

cupsys_1.1.23-10sarge1
cupsys-bsd_1.1.23-10sarge1
cupsys-client_1.1.23-10sarge1
cupsys-driver-gimpprint_4.2.7-10
cupsys-driver-gimpprint-data_4.2.7-10
foomatic-db_20050420-1
foomatic-db-engine_3.0.2-20050403-1
foomatic-db-gimp-print_4.2.7-10
foomatic-db-hpijs_1.5-20050420-1
foomatic-filters_3.0.2-20050403-1
gimp_2.2.6-1
gimp-data_2.2.6-1
gs-esp_7.07.1-9
ijsgimpprint_4.2.7-10
libcupsys2_1.1.23-10sarge1
libcupsys2-gnutls10_1.1.23-10sarge1
libgimp2.0_2.2.6-1
libgimpprint1_4.2.7-10

documented on: 2006.09.26

cups in debian etch, using gimp-print

This is incorrect. The current cupsys-driver-gimpprint package in Etch is just an empty transitional package to ensure an automatic upgrade to the gutenprint system. If you need a fully functional gimpprint then you have to find older packages, maybe on snapshot.debian.net.

aptitude install foomatic-db-engine foomatic-filters foomatic-db-gimp-print
aptitude install gs-esp
aptitude install cupsys cupsys-bsd cupsys-driver-gimpprint

aptitude install escputil

% aptitude install foomatic-db-engine foomatic-filters foomatic-db-gimp-print
The following NEW packages will be installed:
  foomatic-db foomatic-db-engine foomatic-db-gimp-print
  foomatic-db-gutenprint foomatic-filters ijsgutenprint libijs-0.35
The following packages are RECOMMENDED but will NOT be installed:
  cupsys-client lpr lprng rlpr
0 packages upgraded, 7 newly installed, 0 to remove and 780 not upgraded.
Need to get 0B/3358kB of archives. After unpacking 56.4MB will be used.

OK. foomatic-db-gutenprint is not required.

% aptitude install cupsys cupsys-bsd cupsys-driver-gutenprint
The following NEW packages will be installed:
  cupsys cupsys-bsd cupsys-client cupsys-common cupsys-driver-gutenprint
Need to get 0B/3472kB of archives. After unpacking 12.8MB will be used.

Oops no, I don't want gutenprint driver, I want gimpprint driver instead.

% aptitude install cupsys cupsys-bsd cupsys-driver-gimpprint
The following NEW packages will be installed:
  cupsys cupsys-bsd cupsys-client cupsys-common cupsys-driver-gimpprint
  cupsys-driver-gutenprint
Need to get 44.2kB/3516kB of archives. After unpacking 12.8MB will be used.

Hmm…, why still installing cupsys-driver-gutenprint? how about cupsys-driver-gimpprint-data?

% aptitude install cupsys cupsys-bsd cupsys-driver-gimpprint cupsys-driver-gimpprint-data
The following NEW packages will be installed:
  cupsys cupsys-bsd cupsys-client cupsys-common cupsys-driver-gimpprint
  cupsys-driver-gutenprint
Need to get 1433kB/4906kB of archives. After unpacking 14.8MB will be used.
The following packages have unmet dependencies:
  cupsys-driver-gimpprint-data: Depends: cupsys-driver-gimpprint (= 4.2.7-10) but 5.0.0-2 is to be installed.
Resolving dependencies...
The following actions will resolve these dependencies:

Keep the following packages at their current version:
cupsys-driver-gimpprint-data [Not Installed]

$ apt-cache policy cupsys-driver-gimpprint
cupsys-driver-gimpprint:
  Installed: (none)
  Candidate: 5.0.0-2
  Version table:
     5.0.0-3 0
         50 http://mirror.peer1.net unstable/main Packages
     5.0.0-2 0
        600 http://mirror.peer1.net etch/main Packages
     4.2.7-10 0
         30 http://mirror.peer1.net sarge/main Packages

$ apt-cache policy cupsys-driver-gimpprint-data
cupsys-driver-gimpprint-data:
  Installed: (none)
  Candidate: 4.2.7-10
  Version table:
     4.2.7-10 0
         30 http://mirror.peer1.net sarge/main Packages

Software Users Manual

http://localhost:631/sum.html

Admin

http://localhost:631/admin

Setting the Output Order

The the -o outputorder=order option to set the output order of all pages:

lp -o outputorder=normal filename ENTER
lp -o outputorder=reverse filename ENTER
lpr -o outputorder=reverse filename ENTER

N-Up Printing

The -o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:

lp -o number-up=1 filename ENTER
lp -o number-up=2 filename ENTER
lp -o number-up=4 filename ENTER
lpr -o number-up=16 filename ENTER

The -o page-border=value option chooses the border to draw around each page:

-o page-border=double; draw two hairline borders around each page
-o page-border=double-thick; draw two 1pt borders around each page
-o page-border=none; do not draw a border (default)
-o page-border=single; draw one hairline border around each page
-o page-border=single-thick; draw one 1pt border around each page

The -o number-up-layout=value option chooses the layout of the pages on each output page:

-o number-up-layout=btlr; Bottom to top, left to right
-o number-up-layout=btrl; Bottom to top, right to left
-o number-up-layout=lrbt; Left to right, bottom to top
-o number-up-layout=lrtb; Left to right, top to bottom (default)
-o number-up-layout=rlbt; Right to left, bottom to top
-o number-up-layout=rltb; Right to left, top to bottom
-o number-up-layout=tblr; Top to bottom, left to right
-o number-up-layout=tbrl; Top to bottom, right to left

Setting the Brightness

You can control the overall brightness of the printed output using the -o brightness=percent option:

lp -o brightness=120 filename ENTER
lpr -o brightness=120 filename ENTER

Values greater than 100 will lighten the print, while values less than 100 will darken it.

Saving Printer Options and Defaults

Printer Instances

Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash (/) character:

lpoptions -p laserjet/duplex -o sides=two-sided-long-edge ENTER
lpoptions -p laserjet/legal -o media=Legal ENTER

The lp and lpr commands also understand this notation:

lp -d laserjet/duplex filename ENTER
lpr -P laserjet/legal filename ENTER

Removing Instances

Use the -x printer/instance option to remove a printer instance that you no longer need:

lpoptions -x laserjet ENTER
lpoptions -x laserjet/duplex ENTER
lpoptions -x laserjet/legal ENTER

The -x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.

cups admin

start a "stopped" cups printer

/usr/bin/enable $PRINTER; lpc status

lpc

lpc - line printer control program

$ lpc status
hp_psc_1210:
        printer is on device 'usb' speed -1
        queuing is enabled
        printing is enabled
        no entries
        daemon present

Since lpc is geared towards the Berkeley printing system, it is impossible to use lpc to configure printer or class queues provided by CUPS. To configure printer or class queues you must use the lpadmin(8) command or another CUPS-compatible client with that functionality.

lpadmin

lpadmin - configure cups printers and classes

-E
     Enables the printer and accepts jobs; this is the same as  running
     the accept(8) and enable(8) programs on the printer.

printer and class names are not case-sensitive.

lpstat

lpstat - print cups status information

$ lpstat -t
scheduler is running
system default destination: hp_psc_1210
device for hp_psc_1210: usb:/dev/usb/lp0
device for hp_psc_1210/a4: usb:/dev/usb/lp0
device for hp_psc_1210/bw: usb:/dev/usb/lp0
device for hp_psc_1210/draft: usb:/dev/usb/lp0

hp_psc_1210 accepting requests since Jan 01 00:00
hp_psc_1210/a4 accepting requests since Jan 01 00:00
hp_psc_1210/bw accepting requests since Jan 01 00:00
hp_psc_1210/draft accepting requests since Jan 01 00:00

printer hp_psc_1210 is idle.  enabled since Jan 01 00:00
printer hp_psc_1210/a4 is idle.  enabled since Jan 01 00:00
printer hp_psc_1210/bw is idle.  enabled since Jan 01 00:00
printer hp_psc_1210/draft is idle.  enabled since Jan 01 00:00

-t
     Shows  all  status  information.  This  is equivalent to using the
     "-r", "-d", "-c", "-d", "-v", "-a", "-p", and "-o" options.

disable, enable

disable, enable - stop/start printers and classes

SYNOPSIS

disable [ -E ] [ -c ] [ -h server ] [ -r reason ] destination(s)
enable [ -E ] destination(s)

DESCRIPTION enable starts the named printers or classes.

disable stops the named printers or classes.  The following options may
be used:

-c
     Cancels all jobs on the named destination.

The CUPS versions of disable and enable may ask the user for an access password depending on the printing system configuration. This differs from the System V versions which require the root user to execute these commands.

CUPS' error_log FAQ

http://www.linuxprinting.org/error_log-faq.html

Section 1: General Questions

1.1 In which forum should I ask CUPS related questions?
1.2 What is the error log?
1.3 What is the name of the CUPS error log?
1.4 Where is the error_log?

Section 2: Enabling Logging

2.0 See also the Enabling Logging database page.
2.1 How come the error_log doesn't show much information?
2.2 How do I change the logging level?
2.3 After enabling Logging, why are no more error reported to the error_log file?

Section 3: CUPS Log Errors

3.0 See also the CUPS Log Errors database page.
3.1 Why are there no references to ghostscript in the log?
3.2 cupsd: Child exited with status 1!
3.3 unable to evaluate datablob
3.4 cupsdoprint: relocation error: cupsdoprint: undefined symbol: strlcpy
3.5 Warning - hp_psc_950: Bad printcap entry - missing 'sd' or 'client'
3.6 /usr/local/sbin/lpdomatic: unable to evaluate datablob
3.7 media tray empty
3.8 [Job 28] /usr/lib/cups/filter/foomatic-rip: No such file or directory
3.9 "/usr/local/var/spool/cups/d00032-001" - Permission denied
3.10 Denying user "" access to printer?
3.11 /usr/bin/foo2zjs-wrapper: line 141: gs: command not found?
3.12 Unable to convert file 0 to printable format for job 4!
3.13 Couldn't exec foomatic-gswrapper -q?
3.14 Error: /invalidfont in findfont?
3.15 YOU DO NOT HAVE YOUR FONTS INSTALLED!!?
3.16 server-error-service-unavailable?
3.17 sh: line 1: hpijs: command not found
3.18 Can't find initialization file gs_init.ps?
3.19 Unknown device: ijs?
3.20 cat: write error: Broken pipe?

CUPS restart-jobs permission

Newsgroups:  gmane.linux.debian.user
Date:        Wed, 22 Jun 2005 10:52:40 +0100

> I have a _closed_ network (not connected to the internet) on which I have a
> Debian server with CUPS installed.
>
> I have done a fair amount of searching, but I cannot figure out how I can
> configure CUPS to allow _anyone_ to restart a completed job.

There are two main means by which access is retricted to CUPS: IP address and user/group. On 'localhost' (where CUPS) is installed, add yourself/users to group 'lpadmin'.

To provide access from other machines on the network edit cupsd.conf:

<Location /admin>
#
# You definitely will want to limit access to the administration
# functions.
# The default configuration requires a local connection from a user who
# is a member of the system group to do any admin tasks.  You can change
# the group name using the SystemGroup directive.
#

AuthType Basic
AuthClass System

## Restrict access to local domain
Order Deny,Allow
Deny From All
Allow From 127.0.0.1
Allow From 192.168.0.0 (for example)

Clive Menzies

Adobe acrobat printing with CUPS

Date: Tue Feb 26 2002

> I just changed to CUPS, and it works great except I can't get Adobe Reader to
> print. I know I need to change the print command /usr/bin/lpr, but to what?
> I cna't find it in the CUPS docs.

The CUPS client software installs an lpr replacement program that works with CUPS. The /usr/bin/lpr should work fine if you want to print to your default printer. To print to another printer, use:

/usr/bin/lpr -P<print-queue-name>

Keith

How do I start a "not ready" cups printer ?

http://www.linuxquestions.org/questions/showthread.php?s=&postid=869197

We have recently migrated some of our clients to Feodora and configured the printers under cups. When a printer runs out of paper and goes into a "not ready" state, how do you make it "ready" again ! Being a complete linux novice ( my linux support techie is on hols ) I thought i would try lpc start <printer name > but just got the reply start not supported under cups of words to that effect - can anyone help me ! ?

How do I start a "not ready" cups printer ?

> try using some browser to connect to http://<pc[] with cups>:631. this is a
> webinterface for cups.

sorry to be "old fashioned", but I am searching for the ACTUAL COMMAND/S that I can type in in the absence of remote browser access

04-10-2004

documented on: 2004.09.30

printer problem

http://lists.suse.com/archive/suse-linux-e/2002-Dec/1127.html

Date: Wed, 11 Dec 2002 10:25:46 +0000

> If I don't have my printer turned on when I boot SuSE, then I cannot
> print, even if I turn it on later. Is there a way to initiallize the
> printer if I turn it on after I boot Linux? (If I turn on the printer with
> the computer, it works fine.)

If you are using CUPS, try going to Control Center -> System -> Printing Manager, right-clicking the printer, and selecting Start printer.

Kevin Donnelly