Avahi daemon and HAL daemon

[lsatenstein]

I tried to use bugzilla, but got extremely frustrated with the interface. Do the Fedora developers want feedback from we slightly more casual users?

Anyway, when I boot FC5 test 2 I have two failed messages, which are

Avahi Daemon failed

HAL Daemon failed.

I tried to discover how to resolve the boot problem and also how to create a bug report, but gave up. Bugzilla sent me in 6 directions at once.

Can someone, on my behalf, please register the two products as being in need of a fixup?

Leslie
With the Fc5 CD's, there was a clean boot. But packages downloaded with PUP broke my system.

[DougFordham]

This is fixed in the most recent kernel; 2.6.15-1.1881_FC5

Execute a yum update

[Botond]

I'm running 2.6.15-1.1907_FC5 and both avahi and HAL fail to start.
Here's the /var/log/messages for "/usr/sbin/avahi-daemon -D":
Feb 6 11:41:15 levi avahi-daemon[3135]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
Feb 6 11:41:15 levi avahi-daemon[3135]: Successfully dropped root privileges.
Feb 6 11:41:15 levi avahi-daemon[3135]: avahi-daemon 0.6.6 starting up.
Feb 6 11:41:15 levi avahi-daemon[3135]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb 6 11:41:15 levi avahi-daemon[3135]: dbus_bus_get(): Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied

[Botond]

OK, it's a selinux problem. Both avahi and HAL start fine when I set SELINUX mode to permissive (even gnome-power-manager starts now, but udev fails.)

[DougFordham]

Yep, SELinux and a host of other packages have had some problems over the last week. First thing I would do is execute a "yum update", as there have been some recent fixes -- I am updating over 272MB worth of packages as I write this for example. Then reboot and see if your problem is resolved; or if something else breaks ;o)

[DougFordham]

Botond...did you get your problem solved with udev? FWIW, I was having udev problems with another machine that was rectified by today's update.

[Botond]

Yes, udev was fixed by yesterday's updates but Avahi and HAL still don't work. I think HAL is the reason why the automount doesn't work either (even k3b is unable to mount the DVD).
BTW, I've filed a bugreport about it (#180160) and it turned out it's the same as #178702.

[Botond]

Wow, look at this post: http://www.redhat.com/archives/fedora-devel-list/2006-January/msg01219.html
It made my Avahi, HAL and gnome-power-manager working. Even the DVD automount is back.

[DougFordham]

hmmmmm...strange...Tom's post was 24 Jan, and there have been a lot of updates in between that should have corrected that for us; ie, without having to change the label manually. Have to check into that. However, good to know that it solved your problem.

[Botond]

It's strange that on bugzilla they write that selinux-policy-2.2.4 already contains the fix. But I have selinux-policy-2.2.11-1 and still had to manually change the context of that specific file.

[delsvr]

Has this problem been fixed? My HAL daemon continues to fail.

[Flyboy917]

Has this problem been fixed? My HAL daemon continues to fail.

Same issue here. I'm doing a complete re-install with "everything" on another machine as I write this. Will let you know.

[Flyboy917]

Same issue here. I'm doing a complete re-install with "everything" on another machine as I write this. Will let you know.

FYI, I just did a clean re-install with all the development tools included, system tools, and KDE. The HAL and Avahi errors are gone. CD's are automounting fine.
Haven't Yum updated yet....

[DougFordham]

Since this we discussed this, for each subsequent update that I have executed, I have had to manually run the following " chcon -t system_dbusd_exec_t /bin/dbus-daemon " to correct the problem with avahi and hal failing at boot. According to the bugzilla entries, this should not be the case...hopefully, this will be solved in FC5-test3 due out later tomorrow if the build goes as planned.

QUOTE=Botond]It's strange that on bugzilla they write that selinux-policy-2.2.4 already contains the fix. But I have selinux-policy-2.2.11-1 and still had to manually change the context of that specific file.[/QUOTE]

[DougFordham]

...just a quick followup to the questions reference "hal" failing, and if it is fixed. Both hal and avahi function properly, it's just that the selinux policy updates seem to require a "relabel" after each yum update.
************************************************** *********************************
Tom London post on 24Jan06 on the fedora-devel mailing list:
Latest few dbus updates moved dbus-daemon from /usr/bin to /bin.
SELinux label has not yet caught up.

Try changine the label for /bin/dbus-daemon via
chcon -t system_dbusd_exec_t /bin/dbus-daemon

and rebooting. This fixed several dbus/avahi/hal related issues for me.
************************************************** ***********************************

[delsvr]

Hmmm -- I just did a clean FC4 reinstall, no HAL errors. Then I did a yum update -- still no HAL errors.

For reference, I used the yum config and repos as outlined in the fedorafaq. The problem seems to arise only when I upgrade my gnome-2.10 to 2.12. I haven't checked all the dependencies on that install, as I have doubts gnome itself is causing the trouble.

chcon -t system_dbusd_exec_t /bin/dbus-daemon
I tried running this command on my previous install when HAL failed, but my dbus-daemon was still in /usr/bin, and it didn't seem to fix any problems. Has that helped the situation for anyone else? I had selinux-policy 1.27 installed at the time.

[DougFordham]

Should have caught this earlier...you're referencing FC4, when the advice here is mostly specific to FC5. FC5 is a fast moving target and file locations (and other things) can change from one update to the next; I know I am not telling you anything you're not already aware of I am sure, but just want to cover the bases. Anyway, the "chcon..." entry is specific to the issue of dbus-daemon moving from /usr/bin to /bin sometime around late January in FC5; so it shouldn't have any effect on an FC4 install.

[delsvr]

Oops. I should've noticed the forum this was in; I just searched for HAL daemon failures, and this post came up. My apologies.

[DougFordham]

...none required I would think, since we're all here to learn and help...just wanted to make sure that any advice was relevant to your question, and that additional problems weren't created by the application of the wrong data...regards, doug

Oops. I should've noticed the forum this was in; I just searched for HAL daemon failures, and this post came up. My apologies.