-
Notifications
You must be signed in to change notification settings - Fork 16
TIPS: Miscellaneous Tips
Debug logging causes additional messages to be written to the CUPS error logs
(usually at /var/cups/error_log*
). These messages are often important in
diagnosing problems and bugs in Captdriver.
To switch on debug logging, run:
cupsctl --debug-logging
To switch it off, run:
cupsctl --no-debug-logging
There may be a delay when running these commands. If any of the commands fail with a Connection reset by peer error, try repeating the command after waiting a few seconds.
The cupsctl
command should be available on systems where the CUPS
development packages have been installed. The binary is usually found in
/usr/sbin/
.
The directory at /usr/share/cups/usb
contains configuration files
which selectively disables backend features for devices, or excludes
them completely (by "blacklisting").
Devices are targeted in these configuration files by their USB vendor
and product IDs. Instructions on how to use these files should be
included in the first lines of org.cups.usb-quirks
.
PROTIP: list product and vendor IDs of attached USB devices with
lsusb
.
Content in this wiki is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Any errors, omissions or suggestions? File an issue and apply the wiki
label.
Bookmarks
Unofficial Introduction to CAPT (Executive Summary)
Rootless Write Access To USB Devices
Other Canon Printer-Related Projects
SPECS: 0xA1A1
Command and Response Format
Search for pages starting with
-
SPECS
for notes on the operation of the CAPT data formats and communications protocol -
TESTING
for guidelines on testing Captdriver -
TIPS
for potentially helpful information on studying the project or the CAPT format-protocol