Canon UFR II/UFRII LT Printer Driver for Linux Version 3.40 
PLEASE READ THIS DOCUMENT CAREFULLY
CONTENTS
Before Starting
1. Introduction
"Canon UFR II/UFRII LT Printer Driver for Linux" is a Linux operating system printer driver that supports Canon devices. It uses the CUPS (Common Unix Printing System) printing system for Linux operating systems. Installing this driver enables you to print with built-in device functions from the GUI (Graphical User Interface) settings screen and command line.
2. Distribution File Structure of the Printer Driver
This printer driver distribution files are as follows:
README-ufr2-3.4xUS.html (This document)
Describes supplementary information on this driver.
LICENSE-EN.txt
Describes the user license agreement on this driver.
guide-ufr2-3.4xUS.tar.gz
User's guide that explains how to use this driver.
Because this file is in a compressed format, you need to extract it to the appropriate directory before reading.
cndrvcups-common-3.80-1.i386.rpm (for 32-bit)
cndrvcups-common-3.80-1.x86_64.rpm (for 64-bit)
cndrvcups-common_3.80-1_i386.deb (for Debian 32-bit)
cndrvcups-common_3.80-1_amd64.deb (for Debian 64-bit)
Installation package for the CUPS driver common module *
cndrvcups-ufr2-us-3.40-1.i386.rpm (for 32-bit)
cndrvcups-ufr2-us-3.40-1.x86_64.rpm (for 64-bit)
cndrvcups-ufr2-us_3.40-1_i386.deb (for Debian 32-bit)
cndrvcups-ufr2-us_3.40-1_amd64.deb (for Debian 64-bit)
Installation package for this printer driver *
cndrvcups-utility-1.00-1.i386.rpm (for 32-bit)
cndrvcups-utility-1.00-1.x86_64.rpm (for 64-bit)
cndrvcups-utility-1.00-1_i386.deb (for Debian 32-bit)
cndrvcups-utility-1.00-1_amd64.deb (for Debian 64-bit)
Installation package for the Canon Printer Setup Utility
cndrvcups-common-3.80-1.tar.gz
Source file for the CUPS driver common module
cndrvcups-lb-3.40-1.tar.gz
Source file for this printer driver
install.sh
The installer to use when installing the printer driver
* The file name for the CUPS driver common module and printer driver differs depending on the version. Use the combination of installation package versions indicated here.
3. Printer Driver Usage Environment
This printer driver can be used with the following environment.
Hardware
Computer that is enable to operate Linux, with x86 compatible CPU (32-bit or 64-bit)
Evaluated OS
The driver has been confirmed to operate in the following operating systems.
For 64-bit/32-bit
Ubuntu 16.10/17.04 Desktop
Debian 8.6 to 8.8
Fedora 25
For 64-bit
CentOS 7.3
Software
CUPS version 1.2 or later
Install CUPS to the operating system and start it before installing the driver.
The adding of printers and printing must be enabled in the various security services.
Ghostscript
Before printing, install or update the version of Ghostscript that supports the distribution you are using. Ghostscript can be obtained from the website for the distribution.
NOTE
If "opvp" and "oprp" are displayed when the following command is executed, the Ghostscript required for using this driver is installed.
% gs -h | grep opvp
Supported Printer
The printer models supported by this printer driver and the driver files are indicated below.
A separate description is given for models that require bi-directional printing connections and models that use uni-directional printing connections. The communication environment for each model is also indicated. The "<model>" in the driver file name indicates the number or number and letter of the model name.
Models that require bi-directional printing connections
imageRUNNER ADVANCE * (CNCUPSIRADV<model>ZS.ppd)
Uni-directional printing connections are used when the device is connected via USB.
iR-ADV 4525/4535, iR-ADV 4545/4551, iR-ADV 6555/6565, iR-ADV 6575, iR-ADV 8505, iR-ADV 8585/8595
Color imageCLASS MF * (CNCUPSMF<model>CZS.ppd)
MF620C, MF720C, MF8000C, MF8200C, MF8300C, MF8500C
imageCLASS MF (CNCUPSMF<model>ZS.ppd)
MF8000 Series *, MF8300 Series *, MF8400, MF9100/9300, MF9200 Series
iR C1028/C1030 (CNCUPSIRC1030ZS.ppd)
Models that use uni-directional printing connections
imageRUNNER ADVANCE * (CNCUPSIRADVC<model>ZS.ppd)
iR-ADV C255/355, iR-ADV C3320, iR-ADV C3325/3330, iR-ADV C3525/3530, iR-ADV C5535/5540, iR-ADV C5550/5560, iR-ADV C7565, iR-ADV C7580/7570
Color imageRUNNER (CNCUPSIRC<model>ZS.ppd)
iR C1021/C1022, iR C1325/1335 *, iR C3000 Series *
imageRUNNER (CNCUPSIR<model>ZS.ppd)
iR1018/iR1022/iR1023, iR1020/1024/1025, iR1435 *, iR1730/1740/1750, iR2002/2202 *, iR2016/iR2016i, iR2018/iR2018i, iR2020/iR2020i, iR2022/iR2025/iR2030, iR2318/2320, iR2420, iR2422, iR2520, iR2525/2530, iR2535/2545
imagePRESS * (CNCUPSIPRC<model>ZS.ppd)
iPR C700/800, iPR C750, iPR C850
Color imageCLASS LBP * (CNCUPSLBP<model>CZS.ppd)
LBP712C, LBP7660C
imageCLASS LBP * (CNCUPSLBP<model>ZS.ppd)
LBP251, LBP252, LBP253, LBP310/311/312, LBP351/352, LBP6650/3470, LBP6670
imageCLASS MF (CNCUPSMF<model>ZS.ppd)
MF210 Series, MF220 Series, MF230 Series *, MF410 *, MF510 *, MF810/820, MF3010, MF4100, MF4270, MF4320-4350, MF4360-4390, MF4400 Series, MF4500 Series, MF4500w, MF4600, MF4700 Series, MF4800 Series, MF5800 Series, MF5900 Series *, MF6100 Series *, MF7280
MF6530/6550/6560/6580 (CNCUPSMF6500ZS.ppd)
MF7460/7470/7480 (CNCUPSMF7400ZS.ppd)
imageCLASS D (CNCUPSD<model>ZS.ppd)
D400-450, D460-490, D500 Series, D530/D560, D570 *, D1100, D1300/MF6700 *, D1500 *
FAXPHONE (CNCUPSL<model>ZS.ppd)
L90/L160/L230, L100/L150/L170, L190/L410 Series
LC600 (CNCUPSLC600ZS.ppd)
LC800/L3000 (CNCUPSLC3000ZS.ppd)
*: Supports IPv6
4. Installing the Printer Driver
Install the driver after confirming that the computer is connected to an internet environment. For details on the driver installation method and usage method, see the user's guide included with the distribution file.
Cautions When Using
1. Restrictions During Installation (Common to All Distributions)
If you uninstall the driver package with the cache file used for printing remaining in "/etc/cngplp", a warning is displayed because "/etc/cngplp" will not be deleted. The cache file does not need to be deleted. If you want to delete it, manually delete "/etc/cngplp."
If you use a printer with a USB connection, connect multiple printers to one computer, and register a print queue, you may not be able to print or acquire information correctly. This phenomenon can be avoided by having only one printer connected to one computer.
If you are using this driver in a 64-bit environment and update a version 2.00 to 2.20 driver to version 2.30 or later, errors may occur when printing.
This problem can be solved by uninstalling then re-installing the new driver. Alternatively, you can uninstall the old driver instead of updating it, then install the new driver.
If you are using the iR C1021/C1021i, MF8400 Series, MF9100 Series, or MF9300 Series, although IPv6 can be set from the control panel of the printer, only IPv4 supports network connections.
If a printer connected via USB is automatically registered with plug-and-play or if you register a printer connected via USB with the Canon Printer Setup Utility, a printer using uni-directional printing connections is registered, and problems with the color, etc. may occur during printing. The following command must be used to register devices that require bi-directional printing connections.
# /usr/sbin/lpadmin -p [printer name to be registered] -P [PPD file path] -v cnusb:/dev/usb/lp0 -E
Depending on the distribution you are using, when you register the USB printer with the print spooler specifying "/dev/usb/lp*" as the device URI, printing may fail with an error "Printer not Connected" displayed. To solve this problem, specify the printer specific name as the device URI that is displayed by using the following command.
Example: When you use MF4600 Series
(1) Display the device URI
# /usr/sbin/lpinfo -v
direct usb://Canon/MF4600%20Series%20(FAX)
direct usb://Canon/MF4600%20Series%20(PCL5e)
direct usb://Canon/MF4600%20Series%20(PCL6)
direct usb://Canon/MF4600%20Series%20(UFRII%20LT)
(2) Register the printer
# lpadmin -p MF4600_USB -m CNCUPSMF4600ZS.ppd -v usb://Canon/MF4600%20Series%20(UFRII%20LT) -E
If more than two drivers are installed using the LIPSLX, UFR II/UFRII LT (US), and UFR II/UFRII LT (UK) driver install packages, and only one of these drivers is updated, an error will occur. This problem can be solved by updating all of the installed drivers together.
2. Restrictions During Installation (Distribution Specific)
In Fedora/Ubuntu
In Fedora 12 or Ubuntu 9.10, when you change the default options from the CUPS Web interface, the default values will be saved even if there is a conflict between the settings for each function. Also, once the settings are saved with a conflict, you cannot save the settings again even if you use the Web interface to change them to the correct values where there is no conflict. If you display the [cngplp] screen in this situation, an invalid operation may occur. This problem can be avoided by using one of the following methods.
(1) Re-register the printer that performed the invalid operation.
(2) Execute the following command to update CUPS. (Fedora 12 only)
For 64-bit
# yum update cups.x86_64
For 32-bit
# yum update cups.i686
In Fedora 19 or Ubuntu 14.10, if you use the -m option when creating a printer queue using the lpadmin command, the queue may not be displayed in the [cngplp] screen with general user privileges.
In this case, register the printer from the Canon Printer Setup Utility. When registering a printer using the lpadmin command, specify -P instead of -m as the PPD file specifying option. If you specify the PPD with -P, specify an absolute path or relative path as the path to the specified PPD file.
Example:
# /usr/sbin/lpadmin -p [printer name to be registered] -P [PPD file path] -v lpd:[device URI] -E
In Ubuntu 10.10 and later, or Fedora 14 and later, if you register a printer in a state where the language environments of the driver and the operating system differ, the default page size may switch to a size that matches the language environment of the operating system. This problem can be avoided by using one of the following methods to register the printer.
(1) Register the printer after changing the language environment of the operating system to match the driver.
(2) Use the Canon Printer Setup Utility.
(3) When using the lpadmin command, specify -P instead of -m as the PPD file specifying option.
Specify a fully-qualified path name or relative path name for the specified PPD file.
Example:
# /usr/sbin/lpadmin -p [printer name for registration] -P [PPD file path] -v lpd:[device URI] -E
(4) Add "DefaultPaperSize Auto" to "/etc/cups/cupsd.conf", then register the printer after restarting CUPS.
In Fedora/CentOS
You may not be able to install the driver due to a lack of necessary packages. If this happens, you can solve the problem by adding packages using the following commands.
For 64-bit
<Fedora 10>
# yum install glibc.i386
<Fedora 11>
# yum install glibc.i586
<Fedora 12 to 17>
# yum install glibc.i686
<Fedora 18 to 21>
# yum install pangox-compat
# yum install glibc.i686 *1
<Fedora 22>
# dnf install pangox-compat
# dnf install glibc.i686 *2
# dnf install libgcc.i686 *2
# dnf install libstdc++.i686 *2
# dnf install libxml2.i686 *2
<Fedora 23 and later, or CentOS 7.3>
# dnf install libglade2
# dnf install glibc.i686 *2
# dnf install libgcc.i686 *2
# dnf install libstdc++.i686 *2
# dnf install libxml2.i686 *2
For 32-bit
<Fedora 18 to 21>
# yum install pangox-compat
<Fedora 22>
# dnf install pangox-compat
<Fedora 23 and later>
# dnf install libglade2
*1 There may be cases where installation of the 64-bit library of the same name (newest version) is required.
Example:
If the library installation fails with the command "yum install glibc.i686," this may be remedied by executing "yum install glibc.i686" after installing 64-bit glibc library with the command "yum install glibc."
*2 There may be cases where installation of the 64-bit library of the same name (newest version) is required.
Example:
If the library installation fails with the command "dnf install glibc.i686," this may be remedied by executing "dnf install glibc.i686" after installing 64-bit glibc library with the command "dnf install glibc" or upgrading an already installed library with the command "dnf upgrade glibc."
In Fedora
If you are using Fedora 22 and later, although a warning may be displayed saying that the yum command is being deprecated when you install the driver, upgrade the driver, or run the installer, installation is performed correctly and no problems will occur.
In Ubuntu/Debian
When installing with the default settings, you may not be able to install the driver due to a lack of necessary libraries. You can solve the problem by installing libraries using the following commands.
For 64-bit
<Ubuntu 12.04 to 13.04>
# apt-get install libglade2-0
# apt-get install ia32-libs
<Ubuntu 13.10 and later, or Debian 8.6 and later>
# apt-get install libglade2-0
# apt-get install libxml2:i386
# apt-get install libstdc++6:i386
For 32-bit
# apt-get install libglade2-0
If you are using Ubuntu 7.04 to 9.04 or Debian 3.1 to 5.0, the libcupsys2 library is required to install the common module. You can install the libcupsys2 library by executing the following command.
# apt-get install libcupsys2
In Ubuntu
If you are using Ubuntu 13.10, when creating a print queue with the lpadmin command, if you use the -m option the printer is registered as a Local Raw printer and not registered correctly. This can be avoided by using one of the following methods.
(1) Specify -P instead of -m as the PPD file specifying option when registering the printer.
If you specifying the PPD file with -P, specify an absolute path or relative path in [PPD file path].
# /usr/sbin/lpadmin -p [printer name for registration] -P [PPD file path] -v lpd:[device URI] -E
(2) Execute the following command to update CUPS:
# apt-get install cups
In Debian
If you are using the 64-bit version of Debian 8.6 or later, installation will fail with the default settings of the operating system because 32-bit packages cannot be installed. In this case, it is necessary to change the settings of the operating system to enable 32-bit packages to be installed.
# dpkg --add-architecture i386
# apt-get update
If you change the settings of the operating system to install a 32-bit package, the settings cannot be restored until the 32-bit package is uninstalled.
If you are using Debian GNU/Linux 4.0, a PPD file error may occur when you register the printer (PPD) with the print spooler. To solve this problem, use "-P (full path to the ppd)" instead of -m when you specify the ppd using the command line.
Example:
# /usr/sbin/lpadmin -p iRC5180 -P /usr/share/cups/model/CNCUPSIRC5180ZS.ppd -v lpd://192.168.1.10/iRC5180 -E
If you are using Debian GNU/Linux 5.0.2, the gs-esp module is required to install the common module. You can install the gs-esp module by executing the following command.
# apt-get install gs-esp
In other distributions
If you are using SUSE LINUX Professional 9.3, the driver UI may display unintelligible characters. You can solve this problem using the following method.
(1) Log in as 'root'.
(2) Execute the following command to change the GTK+ environment settings.
# cd /etc/
# ln -s opt/gnome/gtk ./
If you are using SUSE LINUX Professional 9.3, a warning may occur when you activate the driver UI. You can solve this problem using the following method.
(1) Open [K Menu] > [Control Center].
(2) Select [Appearance & Themes].
(3) Select [Colors].
(4) Deselect [Apply colors to non-KDE applications].
(5) Close [Control Center].
3. Restrictions During Printing (Common to All Distributions)
When specifying a value less than 100 for [Brightness and Gamma] in the [General] sheet, due to a cause of operation by Ghostscript, an extra black page may be printed as a last page.
The maximum number of files that can be held in the print queue when printing is 500 according to CUPS specifications. Files queued after the 500th file will be ignored.
When specifying multiple pages/copies for [Page Layout] in the [General] sheet to print a document created with StarSuite7/OpenOffice, due to a cause of operation by the CUPS module, settings are not correctly assigned to the multiple pages and output.
PostScript files created with the number of copies specified in OpenOffice.org or StarSuite are affected not by the value specified by [Copies] in the [cngplp] screen (the driver UI), but by the number of copies set when creating the PostScript file.
If you specify paper source settings in the print screen of an application such as Writer of OpenOffice.org, the settings made from the application are overridden by the printer driver UI settings. To print from the desired paper source, specify the paper source from the printer driver UI beforehand, or print from the command line.
If you are printing a TIFF or JPEG image from the driver UI or command line, the image may be divided and printed across multiple pages. This problem can be solved by outputting the image as a PostScript file from an application such as GIMP, then printing the PostScript file from the driver UI or command line.
After setting an entry or text view value, if you finish by clicking the [X] button at the top right of the dialog box, the value is treated as a valid value in the same way as when you click the [OK] button. If you want to disable the set value, click the [Cancel] button.
If you specify a document name that exceeds 32 bytes when printing, the character string for the document name is deleted from the 33rd byte onward by the driver, and the document name displayed in the device will be a maximum of 32 bytes.
If you print a PDF image file from the [cngplp] screen or command line, the print result may be blacked out, depending on the image.
If you are using an environment in which you can use Adobe Reader 9, you can solve this problem by selecting [Let printer determine colors] or [Print As Image] in the [Advanced Print Setup] dialog box when printing.
If you are printing an image included in a PDF file, you may not be able to print it correctly depending on the program pdftops uses. You can solve this problem by changing the program that pdftops uses with the following command.
<If you are using Ghostscript pdftops>
# lpadmin -p [registered printer name] -o pdftops-renderer-default=pdftops
<If you are using poppler pdftops>
# lpadmin -p [registered printer name] -o pdftops-renderer-default=gs
When printing PDF files using Adobe Reader 8, there may be instances where some image data is not printed. This problem may be solved by printing using Adobe Reader 7 or 9, or setting level 3 in the PostScript options.
Depending on the CUPS version, use of "#" or "\" for lpoptions may not be printed correctly. Do not use these characters.
If you are using CUPS version 1.6.3 or earlier, data may not print correctly after the second time if the printer is automatically registered by connecting the computer and device via USB. This can be avoided by registering the printer again using the Canon Printer Setup Utility.
If settings are changed from the driver UI, during print processing, the printed result will reflect the changed settings.
If your version of Ghostscript is 8.6.x, you may not be able to print some documents.
If [Dept. ID Management Authentication]/[Secured Print Authentication] is not set correctly, you may not be able to use the authentication function or perform printing. If the device supports encryption for authentication information, set [Mode 2]. Otherwise, set [Mode 1].
If [Brightness and Gamma] is specified in the [General] sheet from an application such as OpenOffice.org, GIMP, or Acrobat Reader v.5.0, the settings will be invalid.
When printing from OpenOffice.org, some finishing functions such as [Rotate] may not operate correctly if you specify multiple copies for [Copies] in the driver UI.
If the [Finisher-Q3] or [Saddle Finisher-Q4] is attached and you specify A4, Letter, or Legal as the page size, the document is not printed correctly when you attempt to print with [Binding Location] set to [Short Edge (Top)] and [Staple Position] set to [Top (Double)], or [Binding Location] set to [Short Edge (Bottom)] and [Staple Position] set to [Bottom (Double)], in the [Finishing] sheet.
If you print a TIFF image file from the [cngplp] screen or the command line, the print result may be blacked out, depending on the image. This can be avoided by using one of the following methods.
(1) Print from an application such as GIMP etc.
(2) Output the file as a PostScript file, then print the output PostScript file from the [cngplp] screen.
If you change the output method to [Print] after specifying [Secured Print] as the output method and clicking [Save Settings] in the driver UI, the name of the document you output using [Secured Print] is displayed in the job log of the printer. This problem can be solved by using the [Save Settings] button instead of the [Print] button to print when changing the output method from [Secured Print] to [Print].
Depending on the version of GTK (GIMP Toolkit), some characters may be unintelligible when displayed on the screen, but this does not indicate a problem with the functions and values set. Redraw the corresponding text area to solve this problem.
You cannot print a PDF document by directly specifying it from the desktop or command line. When printing a PDF document, it is recommended that you print it from Acrobat Reader or Adobe Reader.
If you are using Adobe Reader 7.0.x, and modify such settings as paper size, paper source, duplex printing, etc. in the print screen, these options are automatically added to the printer command.
However, these settings will not work because they cannot be recognized as command options. To solve this problem, use -o to separate each command options.
[Before change]
-o InputSlot=Manual,Duplex=DuplexNotumble
[After change]
-o InputSlot=Manual -o Duplex=DuplexNoTumble
When performing 2-sided printing with Adobe Reader 8.1.2, if you specify [ON (Short-edged Binding)] for [Duplex Printing] in the print properties for Adobe Reader 8.1.2, the document will be printed on both sides with long-edged binding. This problem can be avoided by printing the document using the printer driver UI.
There may be instances where MF4270, or L90/L160/L230 printers, depending on the environment and type of print data, cannot print due to a printer data error at the device end. This is caused by a time out error occurring at the device end. This problem can be avoided by turning the error time out setting off at the device.
4. Restrictions During Printing (Distribution Specific)
In Fedora/Ubuntu/CentOS/Debian
If you are printing to a device that supports the authentication information encryption function, you need the beecrypt library for each distribution.
Examples of the beecrypt library installation command are as follows.
For 64-bit
<Fedora 19 to 21>
# yum install beecrypt.i686 beecrypt-devel.i686
<Fedora 22 and later, or CentOS 7.3>
# dnf install beecrypt.i686 beecrypt-devel.i686
<Ubuntu 13.04 to 15.10, or Debian 8.6 and later>
# apt-get install libbeecrypt7:i386 libbeecrypt-dev:i386
<Ubuntu 16.04 and later>
# apt-get install libgcrypt20:i386 libgcrypt20-dev:i386
For 32-bit
<Fedora 19 to 21>
# yum install beecrypt beecrypt-devel
<Fedora 22 to 24>
# dnf install beecrypt beecrypt-devel
<Ubuntu 13.04 to 15.10, or Debian 8.6 and later>
# apt-get install libbeecrypt7 libbeecrypt-dev
<Ubuntu 16.04 and later>
# apt-get install libgcrypt20 libgcrypt20-dev.
If you attempt to print from a color imageRUNNER/i-SENSYS LBP printer using this driver, performance may be decreased if the JPEG library (libjpeg62) is not installed.
You can avoid a reduction in performance by installing libjpeg62 using the following commands.
<Fedora 9/10>
# yum install libjpeg.i386
<Fedora 11>
# yum install libjpeg.i586
<Fedora 12/13>
# yum install libjpeg.i686
<Fedora 14 to 21>
# yum install libjpeg-turbo.i686
<Fedora 22 and later, or CentOS 7.3>
# dnf install libjpeg-turbo.i686
<Ubuntu, or Debian 8.6 and later (32-bit)>
# apt-get install libjpeg62
<Ubuntu, or Debian 8.6 and later (64-bit)>
# apt-get install libjpeg62:i386
In Fedora/Ubuntu
In Fedora 11 and later, or Ubuntu 9.04 and later, when you print banner pages, the specified number of banner pages are printed.
In Fedora 15 and later, or Ubuntu 11.04 and later, when you print with the brightness specified between 0% and 9%, the brightness setting is not applied and the document is printed the same as if the brightness was specified as 100%.
In Fedora 13 and later, or Ubuntu 8.10 and later, when printing PDF data or PS data, brightness and gamma correction settings may not be reflected in the print result.
If you are using Fedora 18 or later or Ubuntu 12.04 or later and the device is connected via USB, data may not print correctly after the second time if you attempt to continuously print the same data. This is caused by a discrepancy occurring in the transfer of data between the device and the operating system.
This problem may be solved by adding the following option after disconnecting the USB cable and resetting the USB port.
# lpadmin -p [printer name for registration] -o usb-no-reattach-default=true
If you are using CUPS version 1.5 or earlier, the problem may be solved by specifying cnusb as follows after disconnecting the USB cable and resetting the USB port.
# /usr/sbin/lpadmin -p [printer name for registration] -P [PPD file path] -v cnusb:/dev/usb/lp0 -E
In Fedora 19 and later, or Ubuntu 8.10 and later, the printer will print with the default paper output method, regardless of whether you have specified the paper output method. This problem can be solved by changing the output paper method setting from the CUPS printer settings (Web).
In Fedora 19 to 21, or Ubuntu 13.04 to 14.04, when you select [Standard], [classified], [secret], [confidential], [topsecret], or [unclassified] in the banner page print settings from the [cngplp] screen or the command line, the selection is not reflected in the printed result.
In Fedora
In Fedora 22 and later, when you print character strings that include multi-byte characters, they may be printed with the spaces between characters in the relevant areas reduced. You can solve this problem by printing from a text editor such as gedit.
In Fedora 22 and later, when you attempt to print 4-byte UTF-8 characters from the [cngplp] screen or a command line, the characters may not be printed. Also, when printing such characters from an app such as gedit, Firefox, etc., they may be illegible. These problems are caused by the system.
When performing banner printing in Fedora 8/9, if you specify a setting other than [None] for [End] under [Banner] in the [General] sheet, the print queue will stop.
In Fedora 11, when you print with the print queue stopped after canceling a job, the job is suspended. In this case, click the [Maintenance] button in printers in the CUPS Web interface and select [Resume Printer] to perform the [pending since] job again.
If you cannot find the [Maintenance] button, you can select [Resume Printer] by selecting [Pause Printer].
When you print a TIFF or JPEG file from the driver UI or command line in Fedora 13 to 22, the printed image may be broken up. This problem can be solved by outputting the file as a PostScript file from an application such as GIMP, then printing from the command line by typing the PostScript command used to output the file after the [cngplp] screen.
In Fedora 13 and later, even if you specify the brightness and gamma settings from the driver UI or the command line, these settings are not applied to the printed result from the second page onward. This is due to these functions not being enabled because Ghostscript does not correctly recognize the PostScript data created by the application.
In Fedora 20, the department ID management function may not be effective even if you set the department ID management function in the [cngplp] screen or command line (cnjatool). You can solve this problem by updating CUPS with the following command:
# yum install cups
If you attempt to print from a color imageRUNNER/i-SENSYS LBP printer using this driver in a 64-bit version of Fedora 9 to 20 system environment, printing results may not be satisfactory. This is because when the 64-bit packages are installed by the standard installation method, the 32-bit JPEG library is not installed.
This problem can be avoided by executing the following command to install an extra package.
<Fedora 9/10>
# yum install libjpeg.i386
<Fedora 11>
# yum install libjpeg.i586
<Fedora 12/13>
# yum install libjpeg.i686
<Fedora 14 to 18>
# yum install libjpeg-turbo.i686
<Fedora 19/20>
# yum install libstdc++.i686
# yum install libjpeg-turbo.i686
In CentOS
If you are using CentOS 5.3, you cannot print the number of copies as you specified in Evince. You can solve this problem by printing from other PDF viewers such as Adobe Reader or using the following methods.
(1) Set the number of copies to 1 and select a PS command for the output destination in Evince to output a file.
(2) Print the PS command output as a file after specifying the number of copies in the [cngplp] screen.
In Ubuntu
In Ubuntu 13.10 and later, when you print text data that includes multi-byte character code from the [cngplp] screen or the command line, the print result may include incoherent characters or printing may fail. If this happens, the problem can be solved by printing from a text editor such as gedit.
In Ubuntu 8.10, specifying reverse order for printing does not affect the print result. This problem can be solved by updating CUPS.
If you are using Ubuntu 9.04 and update the CUPS version to "1.3.9-17ubuntu3.2", printing will fail due to improper PS data. This problem can be avoided by executing the following command to downgrade the CUPS version to "1.3.9-17ubuntu3.1."
# apt-get install cups=1.3.9-17ubuntu3.1
If you are using Ubuntu 11.10 to 13.04 and attempt to continuously print the same data, the data may not print correctly after the second time. You can solve this problem by updating CUPS with the following commands.
# apt-get install cups
# apt-get install libcups2
If you are using Ubuntu 12.10, and try to print a PDF image from the [cngplp] screen or command line, the PDF image may not print correctly. This can be avoided by using one of the following methods.
(1) Print from another PDF viewer application such as Adobe Reader.
(2) Edit "/usr/share/cups/mime/cupsfilters.convs" as follows then restart CUPS.
[Before change]
# application/pdf application/vnd.cups-postscript 66 pdftops
# application/postscript application/vnd.cups-postscript 66 pstops
[After change]
application/pdf application/vnd.cups-postscript 33 pdftops
application/postscript application/vnd.cups-postscript 33 pstops
In Debian
In Debian GNU/Linux 4.0, you may take time to print from Evince or may not be able to print some documents. To solve this problem, print the document from other application.
If you are using Debian GNU/Linux 4.0 r6, and attempt to print a text file using the printer driver UI when EUC-JP is set as the locale, printing will fail. This problem can be solved by printing a PS command created with a text editor or text/Postscript conversion program such as paps.
In other distributions or combinations of distributions
If you are using OpenSUSE 10.2 or SUSE Linux Enterprise Desktop 10 SP1, which includes Ghostscript version 8.15.3, you may not be able to print some documents. To solve this problem, install another version of Ghostscript.
If you are using OpenSUSE 11.0 with Ghostscript version 8.6.x, printing from Evince, GIMP, or other applications may take time.
Although Okular is the standard document viewer in the OpenSUSE 11.1 KDE environment, the printer driver functions do not operate correctly with it. You can solve this problem by using another application such as Acrobat Reader etc.
If you are using Vine Linux 3.1, you may take time to print from Adobe Reader 7.0.9 or may not be able to print some documents.
When printing PDF files containing Japanese characters from the command line in Vine Linux 4.1, there may be instances where Ghostscript terminates unexpectedly, causing printing to stop.
This problem can be avoided by printing PDF files using Adobe Reader.
When printing PDF files from Adobe Reader 8 in Vine Linux 4.1, there may be instances where Ghostscript terminates unexpectedly, causing the print queue to stop. This is caused by Ghostscript (7.07) not being able to analyze PS files created by Adobe Reader 8, and consequently terminating prematurely, thereby stopping the filtering process. This problem can be avoided by using Adobe Reader 7.
When printing text files in landscape orientation in Vine Linux 4.1/4.2, Fedora 8/9, or Red Hat Enterprise Linux v.5, there may be instances where the text file is printed in portrait orientation with some of the print data not being printed on the page. This is caused by the CUPS filter employed by the distribution you are using creating a PS command that is already set to portrait. Also, some of the functions provided in the CUPS standard filter "texttops" may not operate correctly. This problem can be avoided by changing the CUPS filter name specified in the "text/plain" entry line in the CUPS setting file "mime.convs" to the CUPS standard filter "texttops."
This will result in Japanese characters being misprinted, therefore when printing Japanese characters, it is necessary to print a PS command created with a text editor or text/PostScript conversion program such as paps.
If you are using SUSE Linux 9.3 or 10.0, and are printing from the print screen of Mozilla or FireFox, because the multiple copies setting is not enabled, you can print only one copy regardless of how many copies you have specified. This problem can be solved by changing the following line in the file "/etc/cups/mime.convs."
[Before change]
application/mozilla-ps application/postscript 33 pswrite
[After change]
application/mozilla-ps application/postscript 33 pstops
If you are using Mandriva One 2008 Spring or Mandriva 2008 PowerPack with CUPS version 1.3.6, unintended print results may occur even when printing with standard CUPS print functions. This problem can be solved by updating CUPS.
Appendix
A list of the license modules including in this driver is indicated below.
Schedule 1 (The software programs of this driver)
CANSRGBA.ICC/ CNC610A.ICC/ CNC610B.ICC/ CNC710A.ICC/ CNC710B.ICC/ CNC711A.ICC/ CNC711B.ICC/ CNC810A.ICC/ CNC810B.ICC/ CNC910A.ICC/ CNC910B.ICC/ CNCA10A.ICC/ CNCA10B.ICC/ CNCB10A.ICC/ CNCB10B.ICC/ CNCC10A.ICC/ CNCC10B.ICC/ CNCD11A.ICC/ CNCD11B.ICC/ CNCE10A.ICC/ CNCE10B.ICC/ CNCF10A.ICC/ CNCF10B.ICC/ CNCG10A.ICC/ CNCG10B.ICC/ CNCG11B.ICC
CNCH10A.ICC/ CNCH10B.ICC/ CNCI10A.ICC/ CNCI11B.ICC/ CNCJ10A.ICC/ CNCJ10B.ICC/ CNL610A.ICC/ CNL610B.ICC/ CNL611A.ICC/ CNL611B.ICC/ CNL760A.ICC/ CNL760B.ICC/ CNL810A.ICC/ CNL810B.ICC/ CNL820A.ICC/ CNL820B.ICC/ CNL821A.ICC/ CNL821B.ICC/ CNL960A.ICC/ CNL960B.ICC/ CNL980A.ICC/ CNL980B.ICC/ CNLA60A.ICC/ CNLA60B.ICC/ CNLA80A.ICC/ CNLA80B.ICC/ CNLB10A.ICC/ CNLB10B.ICC/ CNLC10A.ICC/ CNLC10B.ICC
CNLD10A.ICC/ CNLD10B.ICC/ CNLD80A.ICC/ CNLD80B.ICC/ CNLE60A.ICC/ CNLE60B.ICC/ CNLF10A.ICC/ CNLF10B.ICC/ CNLG10A.ICC/ CNLG10B.ICC/ CNLH60A.ICC/ CNLH60B.ICC/ CNLH80A.ICC/ CNLH80B.ICC/ CNLI10A.ICC/ CNLI10B.ICC/ CNLJ80A.icc/ CNLJ80B.icc/ CNLK80A.icc/ CNLK80B.icc/ CNLL10A.icc/ CNLL10B.icc/ CNLM10A.icc/ CNLM10B.icc/ CNZ005.ICC/ CNZ006.ICC/ CNZ007.ICC/ CNZ008.ICC/ CNZ055.ICC
CnLB0021.DAT/ CnLB0052.DAT/ CnLB0089.DAT/ CnLB0203.DAT/ CnLB035C.DAT/ CnLB03C2.DAT/ CnLB050F.DAT/ CnLB065C.DAT/ CnLB0729.DAT/ CnLB0953.DAT/ CnLB0A87.DAT/ CnLB0C13.DAT/ CnLB0CCA.DAT/ CnLB0DD6.DAT/ CnLB0E99.DAT/ CnLB10F8.DAT/ CnLB1104.DAT/ CnLB1A99.DAT/ CnLB12B9.DAT/ CnLB1F1F.DAT/ CnLB1493.DAT/ CnLB157C.DAT/ CnLB15C8.DAT/ CnLB1732.DAT/ CnLB174D.DAT/ CnLB1DA1.DAT/ CnLB2030.DAT/ CnLB2289.DAT/ CnLB22F7.DAT
CnLB2325.DAT/ CnLB242B.DAT/ CnLB26EB.DAT/ CnLB2775.DAT/ CnLB2887.DAT/ CnLB2C08.DAT/ CnLB3124.DAT/ CnLB3295.DAT/ CnLB33CE.DAT/ CnLB33E5.DAT/ CnLB3547.DAT/ CnLB3645.DAT/ CnLB3DEA.DAT/ CnLB3E20.DAT/ CnLB3E25.DAT/ CnLB3FEB.DAT/ CnLB3FFE.DAT/ CnLB402B.DAT/ CnLB44F9.DAT/ CnLB4758.DAT/ CnLB4896.DAT/ CnLB495F.DAT/ CnLB4984.DAT/ CnLB49AC.DAT/ CnLB4A33.DAT/ CnLB4B7B.DAT/ CnLB4CAF.DAT/ CnLB4DC9.DAT/ CnLB50B6.DAT
CnLB511D.DAT/ CnLB51C4.DAT/ CnLB5286.DAT/ CnLB5736.DAT/ CnLB582E.DAT/ CnLB5BD1.DAT/ CnLB5BE6.DAT/ CnLB5D7D.DAT/ CnLB5F49.DAT/ CnLB64C1.DAT/ CnLB682C.DAT/ CnLB6A54.DAT/ CnLB6C81.DAT/ CnLB6CC9.DAT/ CnLB6CE8.DAT/ CnLB6D8B.DAT/ CnLB71AF.DAT/ CnLB75F3.DAT/ CnLB7754.DAT/ CnLB789E.DAT/ CnLB7AAC.DAT/ CnLB7C4F.DAT/ CnLB7D50.DAT/ CnLB7D56.DAT/ CnLB7E3A.DAT/ CnLBE76C.DAT/ CnLB7E89.DAT/ CnLBECB5.DAT/ CnLB7FED.DAT/ CnLB7FF3.DAT/ CnLB8018.DAT/ CnLB8037.DAT
CnLB82F5.DAT/ CnLB8568.DAT/ CnLB8773.DAT/ CnLB88EC.DAT/ CnLB8925.DAT/ CnLB8A05.DAT/ CnLB8AEC.DAT/ CnLB8AF4.DAT/ CnLB9005.DAT/ CnLB9053.DAT/ CnLB91CD.DAT/ CnLB9238.DAT/ CnLB9263.DAT/ CnLB92C7.DAT/ CnLB9311.DAT/ CnLB96C4.DAT/ CnLB9724.DAT/ CnLB99D2.DAT/ CnLB9B6F.DAT/ CnLB9C65.DAT/ CnLB9F62.DAT/ CnLBA028.DAT/ CnLBA22F.DAT/ CnLBA2A9.DAT/ CnLBA633.DAT/ CnLBA6A8.DAT
CnLBA7E1.DAT/ CnLBA811.DAT/ CnLBAAB9.DAT/ CnLBAC02.DAT/ CnLBAD22.DAT/ CnLBAE22.DAT/ CnLBB00D.DAT/ CnLBB051.DAT/ CnLBB57D.DAT/ CnLBB74A.DAT/ CnLBB8C5.DAT/ CnLBBC70.DAT/ CnLBBC77.DAT/ CnLBBD1A.DAT/ CnLBBD75.DAT/ CnLBBFAD.DAT/ CnLBC025.DAT/ CnLBC031.DAT/ CnLBC07C.DAT/ CnLBC0B5.DAT/ CnLBC0BB.DAT/ CnLBC12E.DAT/ CnLBC19C.DAT/ CnLBC19E.DAT/ CnLBC41F.DAT
CnLBC4C1.DAT/ CnLBC501.DAT/ CnLBC60E.DAT/ CnLBC61C.DAT/ CnLBC662.DAT/ CnLBC761.DAT/ CnLBC7E9.DAT/ CnLBC9E1.DAT/ CnLBCA28.DAT/ CnLBCAA4.DAT/ CnLBCFCA.DAT/ CnLBD2A2.DAT/ CnLBD37D.DAT/ CnLBD4C7.DAT/ CnLBD5ED.DAT/ CnLBD635.DAT/ CnLBD750.DAT/ CnLBD757.DAT/ CnLBD876.DAT/ CnLBD9BD.DAT/ CnLBDAB4.DAT/ CnLBDC35.DAT/ CnLBDDBE.DAT/ CnLBDE79.DAT/ CnLBDE7B.DAT
CnLBDF09.DAT/ CnLBDFA3.DAT/ CnLBE1E7.DAT/ CnLBE2B8.DAT/ CnLBE418.DAT/ CnLBE71E.DAT/ CnLBE726.DAT/ CnLBE82F.DAT/ CnLBEA17.DAT/ CnLBEAC8.DAT/ CnLBEB13.DAT/ CnLBEEA4.DAT/ CnLBEF52.DAT/ CnLBF017.DAT/ CnLBF066.DAT/ CnLBF2D0.DAT/ CnLBF5F6.DAT/ CnLBF924.DAT/ CnLBFA5E.DAT/ CnLBFB32.DAT/ CnLBFC60.DAT/ CnLBFDB2.DAT/ CnLBFDDF.DAT/ CnLB_04A.DAT/ CnLB_08A.DAT
CnLB_10A.DAT/ CnLB_12A.DAT/ CnLB_13A.DAT/ CnLB_14A.DAT/ CnLB_15A.DAT/ CnLB_16A.DAT/ CnLB_18A.DAT/ CnLB_19A.DAT/ CnLB_21A.DAT/ CnLB_23A.DAT/ CnLB_24A.DAT/ CnLB_26A.DAT/ CnLB_27A.DAT/ CnLB_28A.DAT/ CnLB_29A.DAT/ CnLB_30A.DAT/ CnLB_32A.DAT/ CnLB_34A.DAT/ CnLB_35A.DAT/ CnLB_36A.DAT/ CnLB_38A.DAT/ CnLB_40A.DAT/ CnLB_41A.DAT/ CnLB_42A.DAT/ CnLB_43A.DAT
CnLB_44A.DAT/ CnLB_45A.DAT/ CnLB_46A.DAT/ CnLB_47A.DAT/ CnLB_48A.DAT/ CnLB_49A.DAT/ CnLB_50A.DAT/ CnLB_51A.DAT/ CnLB_52A.DAT/ CnLB_53A.DAT/ CnLB_54A.DAT/ CnLB_55A.DAT/ CnLB_57A.DAT/ CnLB_58A.DAT/ ThLB_27A.BIN/ ThLB_28A.BIN/ ThLB_40A.BIN/ ThLB_41A.BIN/ ThLB_48A.BIN/ ThLB_49A.BIN
CNCC.PRF/ c3pldrv/ cnsetuputil/ cnsetuputil.png/ libc3pl.so.0.0.1/ libcaepcm.so.1.0/ libcaiousb.so.1.0.0/ libcaiowrap.so.1.0.0/ libcanon_slim.so.1.0.0/ libColorGear.so.0.0.0/ libColorGearC.so.1.0.0
cnpkbidi/ cnpkmoduleufr2/ libEnoJBIG.so.1.0.0/ libEnoJPEG.so.1.0.0/ libcaiocnpkbidi.so.1.0.0/ libcanonufr2.la/ libcanonufr2.so.1.0.0/ libcnlbcm.so.1.0/ libufr2filter.so.1.0.0/ cnpkbidi_info_000.xml/ cnpkbidi_info_001.xml/ cnpkbidi_info_002.xml/ cnpkbidi_info_003.xml/ cnpkbidi_info_004.xml
Schedule 2 (The free software components licensed under GNU General Public License Version 2)
*.ppd/ *.res/ cnusb/ cngplp/ cnjatool/ cngplp.mo/ cngplp.glade/ canon-laser-printer.usb-quirks/ cnsetuputil.desktop/ cnsetuputil.mo/ install.sh/ installer_de_ufr8.lc/ installer_en_ufr8.lc/ installer_es_ufr8.lc/ installer_fr_ufr8.lc/ installer_it_ufr8.lc/ installer_ja_ufr8.lc/ installer_ko_ufr8.lc/ installer_zh_CN_ufr8.lc/ installer_zh_TW_ufr8.lc
cngplp_ufr2.glade/ common_ufr2.res/ func_config_ufr2.xml/ libuictlufr2.1.0.mo/ libuictlufr2.la/ libuictlufr2.so.1.0.0/ pstoufr2cpca
Schedule 3 (The free software components)
buflist.h/ buftool.h/ libbuftool.a/ libcanonc3pl.so.1.0.0
cnpklibufr2.h/ libcnpkufr2.a/ libcnpkufr2.la
Support
This software and related information are independently developed by Canon and distributed by your Canon local company. Canon (as a manufacturer of printers supporting this software and related information) and your Canon local company (as a distributor), will not respond to any inquiries about this software or related information. However, any inquiries about printer repair, consumable supplies, and devices should be directed to your Canon local company.

Trademarks
Product and company names herein may be the trademarks of their respective owners.

Copyright CANON INC. 2004