[cups.bugs] [MOD] STR #2676: Scheduler does not start if CUPS is started very shortly after the avahi daemon

[Till Kamppeter]

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

We intend to let CUPS print queues get broadcasted via DNS-SD in Ubuntu, so
that Mac clients see printers shared by Ubuntu boxes.

Problem is the startup of CUPS at boot time. CUPS must start after avahi,
so that it makes use of avahi to do DNS-SD broadcasting. Therefore we
changed the boot sequence and no CUPS starts immediately after avahi got
started. Problem is that when the avahi startup script exits, the avahi
daemon is not really ready and so CUPS detects the daemon and tries to
talk with it but due to getting a bad or no answer CUPS crashes. This only
happens if CUPS shares at least one printer.

CUPS should be tolerant with this and not crash, as it detected the daemon
and so avahi is there and intended to be used it should retry after some
seconds or at least after the broadcast interval (usually 30 sec) has
passed and the next broadcast is due.

It would also be great if CUPS would regularly recheck for a running
avahi-daemon (as it rechecks for configuration changes of local network
interfaces). Then it would even not matter at all whether CUPS or avahi is
started first (but the crash needs to be fixed anyway).

See also

https://bugs.launchpad.net/ubuntu/hardy/+source/avahi/+bug/183652

This bug report and its duplicates contain error_logs of the CUPS crashes.

Link: http://www.cups.org/str.php?L2676
Version: 1.3.5