Comment 15 for bug 56426

I've read through all of these posts and can't really find a reason why avahi-daemon would be turned off by default? And moreover, services-admin should be able to turn avahi on.

Right now, services-admin and the init.d script both have no effect on avahi starting so even a CLI user would not know what is going on. Also, my computer tries to start avahi at boot but it fails. Nothing more is outputted.

What are people supposed to do that have no concept about the command line, init scripts or dbus? For a GUI user, there is no way to get this working. There is a bug if you are required to go reading through bash scripts to get avahi working and it should be fixed.

Also, Sebastien is right. There should be something on the FAQ about this to make this information more accessable to users.