hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-11-24 21:35:17 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

Printing: Create get-printer-attributes output by --ippserver

Browse source 
If --ippserver is specified, output of get-printer-attributes request
from ipptool is created in format compatible with ippeveprinter printer
application, which helps during debugging.
This commit is contained in:
Zdenek Dohnal 2022-02-16 09:06:13 +01:00
parent 57d0f5ff2d
commit 58ca99b19f
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
modules/ROOT/pages/_partials/proc_cups-identifying-your-problem-area.adoc
View file

@ -262,10 +262,10 @@ It is CUPS implementation of IPP everywhere standard, available as a special pri
Because the created PPD file depends on IPP communication with printer, we need info which is gathered from the device. You can use [command]`ipptool` for that: Because the created PPD file depends on IPP communication with printer, we need info which is gathered from the device. You can use [command]`ipptool` for that:
---- ----
$ ipptool -tv <your_printer_device_uri> get-printer-attributes.test &> ipptool_log $ ipptool --ippserver ipptool.attr <your_printer_device_uri> get-printer-attributes.test
---- ----
Attach the created [filename]`ipptool_log` to the bugzilla ticket if needed. Attach the created [filename]`ipptool.attr` to the bugzilla ticket if needed.
==== cups-filters 'driverless' driver ==== cups-filters 'driverless' driver
@ -274,7 +274,7 @@ Cups-filters special driver which is used for generating PPD according IPP Every
We need get-printer-attributes request output too: We need get-printer-attributes request output too:
---- ----
$ ipptool -tv <your_printer_device_uri> get-printer-attributes.test &> ipptool_log $ ipptool --ippserver ipptool.attr <your_printer_device_uri> get-printer-attributes.test
---- ----
and debug logs from the driver itself when it generates PPD for your device: and debug logs from the driver itself when it generates PPD for your device: