[feisty] avahi-daemon 0.6.17 fail on boot

Bug #107630 reported by Massimo Forti
4
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
Fix Released
Undecided
Kees Cook
Declined for Feisty by Kees Cook

Bug Description

Binary package hint: avahi-daemon

After I update my personal ubuntu from 6.04 to 7.04 I have a avahi daemon problem, it return this:

Timeout reached while wating for return value
Could not receive return value from daemon process.
                                                                         [fail]

Now I'm not be able to mount any device usb + cdrom on my notebook hp pavillion dv1000.

Thanks

description: updated
Revision history for this message
Massimo Forti (slackwarelife) wrote : Re: avahi-daemon 0.6.17 fail in Ubuntu 7.04

I now be able to mount the usb + cdrom device, I had a bad configuration of pam modules, sorry for this notification.

The avahi-daemon still has a problmes, this problem was notified here:

http://ubuntuforums.org/showthread.php?p=2307797

I'm not be able to discover hosts running on my network.

Revision history for this message
Enrique Rodriguez (krm) wrote :

You have apparmor installed?

I have the same problem with avahi-daemon and uninstalling apparmor the problem disapear.

Revision history for this message
Francisco Javier Cuadrado (neok84-deactivatedaccount) wrote :

I have the same problem.

I have a WiFi USB adapter and if I configure the WiFi network in /etc/network/interfaces, avahi-daemon fails on boot.

This is my /etc/network/interfaces file:

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
name zd1201
wireless_channel 3
wireless_mode managed
wireless_essid THOMSON
wireless_key [MY WEP KEY]
address 192.168.0.11
netmask 255.255.255.0
gateway 192.168.0.1

One solution is not configure in /etc/network/interfaces, and when GNOME starts, configure manually the WiFi using Network Manager, but this method is ugly.

I don't know why there isn't a solution.

Changed in avahi:
assignee: nobody → ubuntu-core-dev
Revision history for this message
Daniel Holbach (dholbach) wrote :

Please don't assign bugs to ubuntu-core-dev.

Changed in avahi:
assignee: ubuntu-core-dev → nobody
Revision history for this message
Kees Cook (kees) wrote :

I see this with apparmor installed too, I will try to investigate it further.

Changed in avahi:
status: New → Confirmed
Changed in apparmor:
assignee: nobody → keescook
Revision history for this message
Kees Cook (kees) wrote :

Ah-ha! I've tracked this down. The issue is with how the Feisty AppArmor replaces the "capability" module. If the "apparmor" module hasn't been built, "capability" can't load, meaning Avahi doesn't have what it needs to do its work.

So, the solutions are either:
1) run Gutsy (where this is fixed)
2) get the apparmor-modules built and install (see below)
3) uninstall AppArmor (which removes the /etc/modprobe.d/apparmor file)

Here's how to get your apparmor module installed again, after a kernel upgrade:

 sudo apt-get install apparmor-modules-source
 sudo m-a -v -t prepare
 sudo m-a -v -t -f build apparmor-modules
 sudo m-a -v -t install apparmor-modules
 modprobe apparmor

Changed in apparmor:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.