FAQ (CUPS)
Condition 1:
Sometimes the status information displayed on the status monitor does not change.
Remedy:
If you are using the CUPS system, the status display does not change until printing starts.
Also, if an error is indicated by an LED on the printer, eliminate the cause of that error.
Condition 2:
Data cannot be printed properly when the computer has only a small amount of free space available on the hard disk.
Remedy:
This condition occurs more easily when printing is canceled frequently.
When data is printed, a temporary file is created in /tmp. When a large image is printed, this temporary file also becomes large.
Since the disk space becomes used up as the number of temporary files increases, use the rm command to delete files that begin with bj.
Condition 3:
Lines are sometimes incorrectly printed as thick lines or double lines.
Remedy:
This type of condition sometimes occurs during the scaling process performed internally by Print Filter.
Use a photo retouch application to scale the image file to be printed, then print that image file from the command line mode.
Condition 4:
Please describe the files that are created after Print Filter is installed and the locations of those files.
Remedy:
See "1.3.3 Installation Files and Installation Locations" in the "User's Guide for Print Filter Version 2.50."
Condition 5:
A print error occurs after the job hold operation is executed.
Remedy:
The cause of the problem is that the Linux printer driver is not equipped with a device reset and cannot execute printer reset.
The recovery procedure is described below.
First delete all jobs.
Then execute one of the following:
- Turn off the printer, and then turn it back on again.
- Disconnect the USB cable and then connect the cable again.
- Reboot the system.
Condition 6:
When I use GIMP to print a square, several unwanted dot-shaped marks appear on the right side.
Remedy:
This is a problem in the application.
Condition 7:
Printing is interrupted if the CUPS printer settings are changed while data is printed.
Remedy:
If you use the CUPS Web interface or the lpadmin command to change the CUPS printer setting while the printer is printing, the print job is forcibly canceled and printing is interrupted.
This action is a result of the CUPS specifications.
If the above condition occurs, perform the procedure below.
- Delete all jobs.
- Then execute one of the following:
- Turn off the printer, and then turn it back on again.
- Disconnect the USB cable and then connect the cable again.
- Stop and then start the printer by the CUPS system.
Condition 8:
If I open the printer cover while the printer is printing several pages, subsequent printing is sometimes disabled.
Remedy:
If the printer is printing a document that is several pages long and you open the printer cover immediately after paper is ejected at a page break, subsequent printing may be canceled.
This action is a result of the printer specifications.
If the above condition occurs, perform the procedure below and then reexecute the print jobs.
- Delete all jobs.
- Then execute one of the following:
- Turn off the printer, and then turn it back on again.
- Disconnect the USB cable and then connect the cable again.
- Reboot the system.
Condition 9:
BMP files cannot be printed on Red Hat Linux 9.
Remedy:
This is a problem in CUPS. This has been fixed in CUPS1.1.19 or later.
Condition 10:
If a print job is canceled before completion, the lamp flashes continuously and the next job cannot be printed.
Remedy:
The cause of the problem is that the Linux printer driver is not equipped with a device reset and cannot execute printer reset.
The recovery procedure is described below.
First, log in as root and delete all jobs.
Then execute one of the following:
- Turn off the printer, and then turn it back on again.
- Disconnect the USB cable and then connect the cable again.
- Reboot the system.
Condition 11:
The Filter UI does not start even if I run the bjfilter command with the --gui option.
Remedy:
This is caused by insufficient display setting in Linux.
Login as root and perform the following operations.
- SUSE LINUX Professional 9.1
- Start YaST.
- Start the /etc/sysconfig editor in the system menu.
- Select [Desktop] and then [Display manager], and change the settings of the following items:
DISPLAYMANAGER_REMOTE_ACCESS: yes
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN: yes
- Reboot the system.
- Execute xhost + localhost.
Condition 12:
Messages in the status monitor cannot be displayed in SUSE LINUX 9.1.
Remedy:
This condition occurs on newly installed OS with default settings and no IP address assignment.
Log in as root, and perform the following:
- Open /etc/cups/cupsd.conf with an editor, and add the following.
BrowseAllow 127.0.0.1
BrowseAllow 127.0.0.2
- Reboot the system.