Client Does Not Print After Installation
Support knowledgebase (mmichna_cups_client)
Applies to
SuSE Linux: Version 8.2
Symptom
When configuring the printer during the installation, the server is detected and marked as available.
However, the printer cannot be addressed after the installation.
Cause
The configuration has not been saved during the installation.
Solutions
During the installation:
- Update the package "yast2-printer":
If update packages can be installed at the end of the installation,
install the update of the package "yast2-printer".
In an installed system:
- Manual configuration:
Edit the file
/etc/cups/client.conf
and change the line
#ServerName myhost.domain.com
adapting it to the CUPS network server detected during the installation.
The comment sign must also be removed.
- Configuration with YaST2:
After starting YaST2's printer configuration, select
"Change" -> "Advanced" -> "CUPS client-only configuration".
In the next mask, enter the CUPS network server detected during the installation.
In addition, you have the chance to uninstall those packages not required for the
client-only configuration.
Alternative approach:
The default installation also allows you to run CUPS as a server instead of the client-only
configuration. The pros and cons of the client-only configuration and CUPS as a server
are described in the Administration Guide and in the article
http://sdb.suse.de/en/sdb/html/jsmeix_print-einrichten-81.html.
If you want to run CUPS as a server but you do not have a local printer,
activate the service CUPS:
- CUPS activation with YaST2:
Use YaST2's runlevel editor for this purpose.
- Manual activation of CUPS:
insserv -d cups
rccups start
Keywords: CUPS, PRINTER, PRINT, CLIENT, 8.2, CONFIGURATION
Categories:
Printer
SDB-mmichna_cups_client, Copyright SuSE Linux AG, Nürnberg, Germany
- Version: 23. Apr 2003
SuSE Linux AG - Last generated: 28. Jul 2003 by ip (sdb_gen 1.40.0)