How to submit bug re: kcontrol printers stops cups working
[Sarge with KDE]
I've found what I think are 2 bugs in the way kcontrol sets up
cupsd.conf which stops cupsd running.
kde control center (kcontrol)
Peripherals
Printers
[note 1]
[Administrator mode]
Print Server
Configure Server
Network
Listen to (by default contains Listen: *.631)
Add
enter an address
leave port set at default 631 [2]
This will write an erroneous /etc/cups/cupsd.conf file with lines like
Listen *:631
Listen foobar:631
and attempt to restart cupsd which will give an error in
/var/log/cups/error_log:
StartListening: Unable to bind socket for address c0a8010a:631 - Cannot
assign requested address.
So I think this is a bug with kcontrol, that it writes a broken
configuration file which stops cupsd running.
I think it is also a bug(-ette) in cups that the error message it gives
is unhelpful, and in /etc/init.d/cupsys that it happily reports that it
has restarted cupsd when it hasn't.
(Sorry if this sounds like a rant: you shold see how little hair I now
have left :-)
[1] Incidentally at this point a box pops up saying:
"""""""""""""""""""""""""""""""""""""""""""""""""""
Unable to retrieve the printer list. Error message
received from manager:
Connection to CUPS server failed. Check that the CUPS
server is correctly installed and running. Error:
connection refused.
"""""""""""""""""""""""""""""""""""""""""""""""""""
Why does this happen and what does it mean?
[2] yes, I know - now - but I didn't at the time. Anyway the system
should check erroneous user input rather than silently bork the print
system. IMnshO :-)
--
John Stumbles
Reply to: