I have (several) non-CUPS IPP printers; however, I cannot for the life of my determine the names/paths/whatever of the print queues. :631/ and :631/printers/ are completely unhelpful or return 404. I have no clue how to print to these printers, but OS X and Windows seem to have no problem automatically discovering the names of the print queues (although they won't expose them to me). On Linux however, (and I have searched and searched), I am at a loss. As soon as I get the names of the print queues, I know exactly how to print. Printing on Linux has become so frustrating to me when my print servers aren't running CUPS.

The command line command: ipptool http://192.168.1.102:631 print_pdf The contents of print_pdf: { VERSION 2.0 OPERATION Print-Job REQUEST-ID 5 GROUP operation-attributes-tag ATTR charset "attributes-charset" "utf-8" ATTR naturalLanguage "attributes-natural-language" "en" ATTR uri "printer-uri" "http://192.168.1.102:631 " ATTR name "requesting-user-name" "John" ATTR mimeMediaType "document-format" "application/pdf" FILE "steampunk.pdf" } EDIT: Now I have the error client-error-document-format-not-supported, even though this is the standard application/pdf format. The docs in the repository do not discuss this error too thoroughly. The image below appears to be where the issue is raised, something to do with a ppd file? What could be the issue?

I just installed Arch Linux recently and have noticed some odd behavior with the network printer (a Samsung C1860FW model). I have CUPS connected to the printer with IPP and am using a PPD from FooMatic. Whenever I log in or plug in a flash drive or a USB device, the printer wakes up. Nothing prints, but the printer's touchscreen comes on and it warms up and prepares to print, the same as if I had pressed the power button to wake it up from sleep mode. I changed CUPS logging to debug level and run udisksctl monitor but nothing relevant shows up. However, logging into the console doesn't trigger this; only logging into Plasma. (I don't have any other desktops installed.) This happens when I plug devices into the PC (back or front ports doesn't seem to matter). The PC is connected with Ethernet/CAT5e; printer with WiFi. Both are connected directly to the gateway, there's a switch connected too but it's not in use. The printer includes the "SyncThru Web Service." I can change the length of time that the printer stays warmed up but not what actions cause it to wake up. EDIT: Using Wireshark, the packets are going to port 9400 TCP, which apparently means the TWAIN protocol on Samsung devices, so this has something to do with scanning. (I have it connected as a network scanner too.) EDIT 2: Using NetHogs, I found that colord-sane is sending packets. I also found this but there were no relevant answers as to how to disable this behavior. I will investigate further... EDIT 3: I found two other questions on SE about this same problem: this and this . The only answer was to uninstall colord, which I may have to do. EDIT 4: I renamed the colord service file. Fixed for now.

I have a Xerox AltaLink printer that supports stapling. I can print and staple a job if I go to the embedded web server and upload a document to print with my browser, but it would be much more convenient to be able to print with lpr and from within applications such as PDF viewers. I'm using linux with CUPS 2.4.2. When I run ipptool -tv ipp://altalink.mydomain.com/ get-printer-attributes.test, the output includes: > finishings-supported (1setOf enum) = none,staple,punch,punch-dual-left,bind,edge-stitch,jog-offset,staple-top-left,staple-bottom-left,staple-top-right,staple-bottom-right,edge-stitch-left,edge-stitch-top,edge-stitch-right,edge-stitch-bottom,staple-dual-left,staple-dual-top,staple-dual-right,staple-dual-bottom,punch-dual-left,punch-dual-top,punch-dual-right,punch-dual-bottom,punch-triple-left,punch-triple-top,punch-triple-right,punch-triple-bottom So it seems like all I need to do in the printer job menu is set finishings to staple-top-left to get what I want. Unfortunately, when I use system-config-printer to add the printer and edit its properties, the only available option for finishings is None. If I go to the cups embedded web server on port 631, I get even fewer options. And in the system print dialogs, I don't get any option for finishings. How can I enable stapling either as a default for all jobs (my preference) or at least on a per-job basis?

I am troubleshooting my Raspberry Pi CUPS printer server which is having trouble printing a specific paper size from my Fedora laptop. My printer, connected via USB to my CUPS server, cuts off documents of size 8.5x13 inches. However, this only happens with my laptop with Fedora specifically. Other devices in my network can print the same document size fine. I am suspecting that either my laptop or my Raspberry Pi processes the document size incorrectly. I just need to confirm it. However, the CUPS GUI (through the web interface) does not seem to display the paper size of a specific print job. Is there any way too see the paper size of a queued print job through the command line?

I have set up my printer on CUPS ubuntu, and it can be use via ipp. I haven't config the users yet, but I heard that we can pass username and password via ipp url like this: http://username:password@server:631/printers/MyPrinter For example, John use http://john:password@server:631/printers/MyPrinter to access the printer. And I can login into the cups using root/admin user, and set John enable or disable to use the printer. Can we make this work? And how to make this work? Hope you understand my poor english...

On my network I want to use driverless printing with [IPPEverywhere](https://www.pwg.org/ipp/everywhere.html) using the Linux **CUPS** printing system. I have some network printer which does support driverless printing with IPP only very buggy. One does not print some pdf files, the other doesn't print more than one copy and so on. But they all print very well using its native PPD printer drivers. So I want to present a print server on my network that serves the network printer with its own printer drivers but appear on the network as a (virtual?) full powered IPP device for each network printer. That means in general that the print server is "translating" the driverless IPP print commands from the network clients to the printers legacy print commands, so I have only IPPEverywhere print queues on the network. By default CUPS creates a local print queue that serves the printer either driverless using [IPPEverywhere](https://www.pwg.org/ipp/everywhere.html) or with the legacy driver of the printer using its PPD file. ┏━━━━━━━━━━━━━┓ ┃ localhost ┃ ┃ ┌───────┐ ┃ ┏━━━━━━━━━┓ ┃ │ Queue │═╋════════════════┫ Printer ┃ ┃ └───────┘ ┃ ┗━━━━━━━━━┛ ┗━━━━━━━━━━━━━┛ The idea now is to have a printserver that behaves like a driverless printer on the network: ┏━━━━━━━━━━━━━┓ ┏━━━━━━━━━━━━━┓ ┃ localhost ┃ ┃ printserver ┃ ┃ ┌───────┐ ┃ IPPEverywhere ┃ ┌───────┐ ┃ legacy PPD driver ┏━━━━━━━━━┓ ┃ │ Queue │═╋════════════════┫ │ Queue │═╋═════════════════════┫ Printer ┃ ┃ └───────┘ ┃ ┃ └───────┘ ┃ ┗━━━━━━━━━┛ ┗━━━━━━━━━━━━━┛ ┗━━━━━━━━━━━━━┛ Connecting the printer to the printserver with its legacy driver is no problem. This is the old method (but will become deprecated and removed with upstream CUPS versions). But how can I find the printserver on the network so I can connect to it for example with my Android smartphone and print, using IPPEverywhere?

I am using the comming line ipptool for printing, which is a low-level tool in the CUPS daemon for internet printing. IPP is a HTTP-based protocol for internet printers, most current LAN-based office printers are supporting it. I used the following command for print: ipptool -tv -f /path/to/my.pdf ipp://myprinter.on.mylocal.net/ipp/ printfile.ipp Where my printfile.ipp defines the characteristics/capabilities of my printer, as follows: { OPERATION Print-Job GROUP operation-attributes-tag ATTR charset attributes-charset utf-8 ATTR language attributes-natural-language en ATTR uri printer-uri $uri FILE $filename } What I know for sure: 1. Single-sided PDF printing is working seamlessly. 2. The printer is a relative ordinary HP office printer, 3. Which is capable to print double-sided without any problem (co-workers with Windows can do that). I found this printfile with google and seems working, however any deeper digging about its exact format and specification resulted only cloudy specs and docs. Even the name of the file format of this IPP file is unclear for me. How could I make it to print double-sided?

I am debugging some printing issues on a small LAN, and although I'm fairly sure the issues I'm facing are not related to cups itself, I have been tinkering with the printing protocols that both CUPS and my printers (Konica Minolta Bizhub C224E and C3350) understand. That made me wonder: is it just a matter of knowing which protocols your printers support, or is there any hierarchy between them? From the extensive reading I did, I seem to be able to deduce that LPD is fairly old and IPP(14) the 'new kid on the block', but does this new protocol offer real benefits or not?

OK. So I understand that CUPS works as a Print Spooler, managing print jobs and sending them to printers. I also understand that PPD files describe the feature-set of a printer and that CUPS uses these and filters to interface with the printer, generating an output that the printer can use to print the document (either in PostScript, PCL or whatever proprietary format the printer requires). But I'm confused as to a few aspects of this. Mainly: - How do applications send print jobs to CUPS? - How do applications get print options for whatever printer is selected? DO these come from the PPD file or filter that CUPS uses for the printer? - How does this work when the printer is shared by CUPS over IPP? Does whatever device is sending a print job to CUPS do the processing locally or does the CUPS server do it? If CUPS does it, does that mean that the local device needs the PPD file to get the print options, or does CUPS send this to the local device? - As far as I'm aware, any linux computer will probably use CUPS locally as well for printing, so how does this work in regards to print options and processing the print job into PostScript/PCL etc. Thanks for helping to clear up my confusion.

We have a Debian print server running CUPS. In CUPS we have a Raw print queue configured that connects to our networked printer via IPP. I've also shared this printer to our Windows users via a Samba printer share, using pretty stock standard smb.conf options and CUPS as the backend. When printing directly to the CUPS queue from Windows using IPP (eg. http://cups-server:631/printers/printer-name) , the printer responds quickly and prints almost instantly. However, when printing to the print queue via the shared Samba printer on Windows, the printer takes over 15 seconds to open the Printer Properties window, and the same amount of time to print a test page. Whilst trying to deduce the cause, I've been able to reproduce the issue on two completely separate networks with two different print servers and printers, and numerous different Windows clients, so I am confident it is not specific to my individual installs. Using both IP addresses and host names results in the same behavior. Are there any options or settings that need to be tweaked to speed up printing from Samba shared printers? I am running CUPS 2.2.1 and Samba 4.5.12. I can also reproduce the same behavior on an older server running CUPS 1.7.5 and Samba 4.2.14. My smb.conf follows. Everything is the defaults from the stock Debian smb.conf except for the first 4 options under the Printing heading.
*I've removed all the large blocks of unrelated comments from the default smb.conf* [global] ## Printing ## # Enable the spoolssd Service rpc_server:spoolss = external rpc_daemon:spoolssd = fork # Set minimum spoolssd pool spoolssd:prefork_min_children = 2 # Set printing backend to CUPS printing = CUPS ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = WORKGROUP # Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable its WINS Server # wins support = no # WINS Server - Tells the NMBD components of Samba to be a WINS Client # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both ; wins server = w.x.y.z # This will prevent nmbd to search for NetBIOS names through DNS. dns proxy = no #### Debugging/Accounting #### # This tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Cap the size of the individual log files (in KiB). max log size = 1000 # We want Samba to log a minimum amount of information to syslog. Everything # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log # through syslog you should set the following parameter to something higher. syslog = 0 # Do something sensible when Samba crashes: mail the admin a backtrace panic action = /usr/share/samba/panic-action %d ####### Authentication ####### # Server role. Defines in which mode Samba will operate. Possible # values are "standalone server", "member server", "classic primary # domain controller", "classic backup domain controller", "active # directory domain controller". # # Most people will want "standalone sever" or "member server". # Running as "active directory domain controller" will require first # running "samba-tool domain provision" to wipe databases and create a # new domain. server role = standalone server # If you are using encrypted passwords, Samba will need to know what # password database type you are using. passdb backend = tdbsam obey pam restrictions = yes # This boolean parameter controls whether Samba attempts to sync the Unix # password with the SMB password when the encrypted SMB password in the # passdb is changed. unix password sync = yes # For Unix password sync to work on a Debian GNU/Linux system, the following # parameters must be set (thanks to Ian Kahan for # sending the correct chat script for the passwd program in Debian Sarge). passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . # This boolean controls whether PAM will be used for password changes # when requested by an SMB client instead of the program listed in # 'passwd program'. The default is 'no'. pam password change = yes # This option controls how unsuccessful authentication attempts are mapped # to anonymous connections map to guest = bad user # Allow users who've been granted usershare privileges to create # public shares, not just authenticated ones usershare allow guests = yes #======================= Share Definitions ======================= [homes] comment = Home Directories browseable = no # By default, the home directories are exported read-only. Change the # next parameter to 'no' if you want to be able to write to them. read only = yes # File creation mask is set to 0700 for security reasons. If you want to # create files with group=rw permissions, set next parameter to 0775. create mask = 0700 # Directory creation mask is set to 0700 for security reasons. If you want to # create dirs. with group=rw permissions, set next parameter to 0775. directory mask = 0700 # By default, \\server\username shares can be connected to by anyone # with access to the samba server. # The following parameter makes sure that only "username" can connect # to \\server\username # This might need tweaking when using external authentication schemes valid users = %S # Un-comment the following and create the netlogon directory for Domain Logons # (you need to configure Samba to act as a domain controller too.) ;[netlogon] ; comment = Network Logon Service ; path = /home/samba/netlogon ; guest ok = yes ; read only = yes # Un-comment the following and create the profiles directory to store # users profiles (see the "logon path" option above) # (you need to configure Samba to act as a domain controller too.) # The path below should be writable by all users so that their # profile directory may be created the first time they log on ;[profiles] ; comment = Users profiles ; path = /home/samba/profiles ; guest ok = no ; browseable = no ; create mask = 0600 ; directory mask = 0700 [printers] path = /var/spool/samba printable = yes # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no # Uncomment to allow remote administration of Windows print drivers. # You may need to replace 'lpadmin' with the name of the group your # admin users are members of. # Please note that you also need to set appropriate Unix permissions # to the drivers directory for these users to have write rights in it ; write list = root, @lpadmin Here are relevant printing defaults being set by Samba:
_testparm -sv | grep -Ei --color '(print|drive|spool|devmode)'_ Processing section "[homes]" Processing section "[printers]" Processing section "[print$]" Loaded services file OK. Server role: ROLE_STANDALONE load printers = Yes printcap cache time = 750 printcap name = iprint server = disable spoolss = No addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = logon drive = dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver spoolssd:prefork_min_children = 2 rpc_daemon:spoolssd = fork rpc_server:spoolss = external min print space = 0 max reported print jobs = 0 max print jobs = 1000 printable = No print notify backchannel = No print ok = No printing = cups print command = printer name = use client driver = No default devmode = Yes force printername = No printjob username = %U [printers] path = /var/spool/samba printable = Yes print ok = Yes [print$] comment = Printer Drivers path = /var/lib/samba/printers

I have two CentOS 6 servers running cups and connecting to the same ipp over https printer. Both were installed with the same lpadmin command below. lpadmin -p ptr -v https://username%40mailer.com:p%40ssword@myprintserver.com/printer -E Server 1 was able to print without issue. Cups Name : cups Arch : x86_64 Epoch : 1 Version : 1.4.2 Release : 44.el6 printers.conf AuthInfoRequired username,password Info ptr DeviceURI https://username%40mailer.com:p%40ssword@myprintserver.com/printer Server 2 is not able to print Cups Name : cups Arch : x86_64 Epoch : 1 Version : 1.4.2 Release : 78.el6_9 printers.conf AuthInfoRequired none Info ptr DeviceURI https://username%40mailer.com:p%40ssword@myprintserver.com/printer In /var/log/cups/error_log D [26/Oct/2017:10:31:53 -0400] [Job 220770] Connected to printer... D [26/Oct/2017:10:31:53 -0400] [Job 220770] Connected to my-printserverip:443 (IPv4)... D [26/Oct/2017:10:31:53 -0400] [Job 220770] Getting supported attributes... D [26/Oct/2017:10:31:53 -0400] [Job 220770] ATTR: auth-info-required=none D [26/Oct/2017:10:31:53 -0400] [Job 220770] Backend returned status 2 (authentication required) D [26/Oct/2017:10:31:53 -0400] [Job 220770] Job held for authentication. On Server 2 I tried stoping cups, changing AuthInfoRequired from none to username,password and then starting cups however it doesn't fix it and on the next cups restart just reverts back to none. I tried bouncing cups on Server 1 and it retains the username,password. I then updated Server 1 to version 78.el6_9, uninstalling and reinstalling ptr with the above lpadmin command and now both servers are in the same boat reverting to AuthInfoRequired none and Job held for authentication. Is there something different I need to do with the new version of cups? I have tried passing -o auth-info=username,password, however this appears to make the AuthInfoRequired line disappear all together and results in the same errors in the log as above. Update 1: Testing with CentOS 7 gives expected behavior of automatically populating AuthInfoRequired with username,password CUPS version 1.6.3-26 Update 2: Tried to rpmrepack cups 1.4.2-44 from another CentOS 6 server and rpm downgrade to the prior older version with no success. Update 3: I have started reading the cups source code for my version. It appears the AuthInfoRequired field is automatic set for ipp printers based on if cups see's a password in the DeviceURI, not sure why it's tossing my Auth info out the window.

I have set up a network IPP printer on Solaris 10, but when I send a printing job to the queue, I received failed to commit job (2-0): queue disabled error, any idea why? # lpstat -t scheduler is running no system default destination device for printer: ipp://172.16.138.20/printers/DA1D9C printer not accepting requests since October 13, 2016 12:04:37 AM PDT new destination printer printer is idle. enabled since October 13, 2016 12:14:51 AM PDT. available. # lp -d printer localhost.err printer: failed to commit job (2-0): queue disabled

I've got a printer hooked up to my workstation (running PCLINUXOS2012) by USB. All was well until the last time I tried to apply updates to the packages - it went rather pear shaped - lots of upgrade packages were no longer available from the repositories (this may be coincidental to the printing problem). Since then, only root can see the printer via CUPS unless I make it available to others: [colin@localhost ~]$ lpq lpq: error - no default destination available. [colin@localhost ~]$ su Password: [root@localhost colin]# lpq HP-Deskjet-F4200-series is ready no entries [root@localhost colin]# lpadmin -p HP-Deskjet-F4200-series -u allow:all [root@localhost colin]# su colin -c lpq HP-Deskjet-F4200-series is ready no entries [root@localhost colin]# (but this does not change the cupsd.conf - hence needs to be re-applied each time the system is rebooted). How do I make the change permanent? (Coincidentally, the tool used to configure printers accessed from drakconf (PCLinuxos Control centre) now bombs out with the message "The program terminated abnormally). cupsd.conf below, apologies for repodrucing it in it's entirety, but the running version clearly does not match the documentation supplied (which, for example, reports that 'Browsing' can be 'Yes' or 'No', but nothing get's logged for a value of 'on'). I would have expected the lines below the comments to make the printer available to all - but this does not appear to be the case. LogLevel warn SystemGroup lpadmin root Group sys User lp Port 631 Listen /var/run/cups/cups.sock Browsing On BrowseAddress @LOCAL BrowseOrder allow,deny # this line to make printers 'browseable'.... BrowseAllow all BrowseLocalProtocols CUPS dnssd DefaultAuthType Basic Order allow,deny # this to allow access to the web frontend.... Allow all AuthType Default Require user @SYSTEM # and this one to allow submission of print jobs... Allow all Order deny,allow Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow Require user @OWNER @SYSTEM Order deny,allow Order deny,allow AuthType Default Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow Order deny,allow

I need some recommendations on reasonable and up-to-date literature about network printing, the corresponding protocols (ipp, lpdp, ...), printjob authentication and accounting in heterogenous networks.