Johannes Meixner wrote:
Hello,
On Nov 5 21:34 Marc Chamberlin wrote (shortened):
Bug #553147
To avoid possible further confusion:
The issue here is about openSUSE 11.0!
I.e. with the old YaST printer module yast2-printer-2.16.32 which is known to destroy sometimes /etc/cups/cupsd.conf because it uses the YaST "INI" agent to manipulate cupsd.conf but the "INI" agent is either insufficient for config files like cupsd.conf or nobody can tame the "INI" agent beast to work even for cupsd.conf ;-)
But as far as I remember the "INI" agent did not crash YaST. I.e. the crash here seems to have another reason.
Regardless what the reason was in this case:
When the cupsd config file /etc/cups/cupsd.conf is broken there is a /etc/cups/cupsd.conf.default installed which you can copy to /etc/cups/cupsd.conf as root with cp /etc/cups/cupsd.conf.default /etc/cups/cupsd.conf to start cupsd with a clean default cupsd config file.
If even this does not help (e.g. when the CUPS spool files are totally messed up), see http://en.opensuse.org/SDB:CUPS_-_Reinstalling_the_Printing_System regarding "Reinstalling the Printing System"
Kind Regards Johannes Meixner
Johannes - I updated the bug report because I think you are confused about my point. The issue I am reporting is not about whether the cupsd.conf file is mis-configured or not. The issue of the bug report is about the fact the the printer setup module of YaST is not (apparently) starting up the CUPs daemon, or testing its status, when the user completes the process of setting up a printer. This leads to a great deal of confusion if the user is not aware of this fact, because he/she will expect to be able to print something once the process of setting up the printer is complete. If the CUP's daemon is not running, and the user is unaware of this fact, then the user will be unable to print anything, and left in the dark wondering why... Marc Chamberlin.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org