Timo, I have found what the problem is: If avahi-daemon is not running and cups-browsed has nothing to do (no legacy CUPS broadcasting/browsing configured) it simply stops, making Upstart restarting it.
As you are opting for living without running avahi-daemon (as your router or ISP uses .local) cups-browsed keeps respawning.
As a quick fix respawning van get limited in Upstart, for example to give up after the fifth attempt.
As a real fix I will improve cups-browsed In a future version, staying in a loop and regularly checking whether avahi-daemon appears and starting its work then.
As a workaround for the time being, you can make avahi-daemon running, for example by changing the domain via "domain-name=..." in /etc/avahi/avahi-daemon.conf (or modify your router's configuration). Making avahi-daemon running has also the side effect that computers can communicate about available services.
Timo, I have found what the problem is: If avahi-daemon is not running and cups-browsed has nothing to do (no legacy CUPS broadcasting/ browsing configured) it simply stops, making Upstart restarting it.
As you are opting for living without running avahi-daemon (as your router or ISP uses .local) cups-browsed keeps respawning.
As a quick fix respawning van get limited in Upstart, for example to give up after the fifth attempt.
As a real fix I will improve cups-browsed In a future version, staying in a loop and regularly checking whether avahi-daemon appears and starting its work then.
As a workaround for the time being, you can make avahi-daemon running, for example by changing the domain via "domain-name=..." in /etc/avahi/ avahi-daemon. conf (or modify your router's configuration). Making avahi-daemon running has also the side effect that computers can communicate about available services.