Hello, Kevin, many thanks for this summary. On Jan 20 20:26 Kevin Donnelly wrote (shortened):
a problem in SuSE's CUPS package, and that the fix is to add a hostname to the localhost line in /etc/hosts.
To do this: (su) pico /etc/hosts
Adjust the line: 127.0.0.1 localhost to read: 127.0.0.1 yourhostname localhost Save and exit.
As far as I see there is no error in our CUPS package. As far as I remember the defaults in our CUPS package are <Location /> Allow From 127.0.0.1 Allow From 127.0.0.2 </Location> I.e. only access from the IPs 127.0.0.1 and 127.0.0.2 are allowed by default. 127.0.0.1 is the IP of the name "localhost" and 127.0.0.2 is the IP of the hostname in case of a stand alone system (i.e. when no network configuration was done). As far as I remember for a stand alone system there are in /etc/hosts corresponding lines like 127.0.0.1 localhost 127.0.0.2 linux (if you leave the default hostname "linux" unschnaged). If you did a network configuration then there is no longer the line 127.0.0.2 linux instead there is a line matching your network setup like 192.168.1.1 myhostname Because of the defaults in /etc/cups/cupsd.conf you cannot access the cupsd from 192.168.1.1/myhostname. But you can access it from 127.0.0.1/localhost. If you added Allow From 192.168.1.1 or Allow From 192.168.1.* to the <Location /> section in /etc/cups/cupsd.conf then the access would be possible. You can use YaST to do this (there is a section to configure the "CUPS server"). As far as I know you can alternatively change the settings in the KDE printing tools to which cups server IP they should connect to. As far as I remember KDE printing tools don't access the cupsd by default via 127.0.0.1/localhost but via 192.168.1.1/myhostname. Therefore the KDE printing tools cannot acces the cupsd and the cupsd would respond to the client that the access is denied. Obviously it is an error in the KDE printing tools when they crash because of this. During our tests the KDE printing tools never crashed but showed an appropriate message when the access was denied. As far as I know from several reports the crashes happen only in case of an update from an previous KDE version. Regardless which settings there are in /etc/cups/cupsd.conf (regardless whether this settings are the default settings or any kind of manual settings) and regardless of which kind of response the cupsd sends to client, the client should never crash. This is the same as when a web browser would chrash because of an unexpected response from a web server. Kind regards, Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/