Red Hat Bugzilla – Bug 180160
avahi-daemon fails to start when SELINUX == enforcing
Last modified: 2007-11-30 17:11:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20060202 Fedora/18.104.22.168-2 Firefox/22.214.171.124
Description of problem:
With FC5 test2 + full updates (as of the 5th of january) avahi-daemon, haldeamon and gnome-power-manager fail to start if SELINUX is set to enforcing mode. They are all OK if SELINUX is set to permissive mode.
This gets into /var/log/messages after starting "/usr/sbin/avahi-daemon -D":
avahi-daemon: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
avahi-daemon: Successfully dropped root privileges.
avahi-daemon: avahi-daemon 0.6.6 starting up.
avahi-daemon: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
avahi-daemon: dbus_bus_get(): Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set SELINUX to Enforcing mode
2. Reboot and watch for Avahi and HAL services
Actual Results: Avahi and HAL fail to start
Expected Results: They should have started up properly
I think this is a SELINUX bug but I didn't find a better place to report it.
Morover I think (but I'm not sure) that avahi and HAL were OK right after the fresh FC5T2 DVD install and they got broken with one of the updates.
Yes, this was fixed with selinux-policy-targeted-2.2.6+ ( see bug 178702 ) .
Upgrading to the latest selinux-policy-targeted-2.2.11-1 will fix this problem.
*** This bug has been marked as a duplicate of 178702 ***