Problem | Possible Cause and Solution |
|
|
How do I specify the | It can be specified in the “Add Printer” dialogue of |
IP address of my SMB | the configuration tool, if you don’t use the CUPS |
server? | printing system. Unfortunately, CUPS currently |
| doesn’t allow you to specify the IP address of SMB |
| printers, so you will have to be able to browse the |
| resource with SAMBA in order to be able to print. |
|
|
Some documents | Some versions of CUPS, especially those shipped |
come out as white | with Mandrake Linux before the 8.1 release, have |
pages when printing. | some known bugs when processing PostScript |
| output from some applications. Try upgrading to the |
| latest version of CUPS (at least 1.1.14). Some RPM |
| packages for the most popular distributions are |
| provided as a convenience with this Linux Printing |
| Package. |
|
|
I have CUPS and some | There may be some local options defined in your ~/ |
options (such as N- | .lpoptions file, which are manipulated by the |
up) seem to be always | lpoptions command. These options are always used |
enabled even though I | if not overridden by LLPR settings. To get rid of all |
don’t choose them in | options for a printer, run the following command, |
LLPR. | replacing “printer” with the name of the queue: |
| lpoptions |
|
|
I configured a printer | Most printing systems will not run as the |
to print to a file, but I | but as a special user (usually “lp”). Therefore, make |
get “Permission | sure that the file you have chosen to print to is |
denied” errors. | accessible to the user owning the spooler daemon. |
|
|
On my PCL (or GDI) | Unfortunately, some Unix applications may generate |
printer, I sometimes | |
get error messages | supported by Ghostscript, or even the printer itself |
printing instead of my | in PostScript mode. You can try to capture the |
document. | output to a file and view the results with Ghostscript |
| (gv or ghostview will allow you to do so |
| interactively) and see if you get error messages. |
| However, since the application is probably at fault, |
| contact your software vendor to inform them of the |
| issue. |
|
|
Some color images | This is a known bug in Ghostscript (until GNU |
come out all black. | Ghostscript version 7.05) when the base color space |
| of the document is indexed color space and it is |
| converted through CIE color space. Because |
| Postscript uses CIE color space for Color Matching |
| System, you should upgrade Ghostscript on your |
| system to at least GNU Ghostscript version 7.06 or |
| later. You can find recent Ghostscript versions at |
| www.ghostscript.com. |
|
|
7.19