Possibly makes sense to apply this patch also to disable this function if Avahi is already disabled.
Although perhaps we should still check if Avahi is stopped in this case (in case it was started manually) but not send an alert, or perhaps it makes sense not to do a popup notify at all also perhaps makes sense instead to check if avahi is started at all (this can be done with 'avahi-daemon -c' and not notify if its not (i.e. its already disabled) opinions? ** Attachment added: "patch to disable .local checking if /etc/default/avahi-daemon says its not to be started" http://librarian.launchpad.net/6480728/disable-if-default-disabled.diff -- Avahi behaves badly where there is a unicast .local-domain. https://launchpad.net/bugs/83468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
