avahi-daemon takes 100% CPU right after boot and at every restart of CUPS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
avahi (Debian) |
Fix Released
|
Unknown
|
|||
avahi (Ubuntu) |
Fix Released
|
Critical
|
Till Kamppeter |
Bug Description
When I boot the system and log in avahi-daemon takes 100% CPU and Avahi/mDNS/Bonjour does not work at all, avahi-discover does not get access to anything and does not open its window, until it reaches a timeout and shows an error dialog.
When I restart avahi-daemon with
sudo restart avahi-daemon
avahi-daemon usually gets back to normal not taking significant CPU percentage and answering to avahi-discover correctly. If it takes 100% CPU again I simply do another restart to get it to normal.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: avahi-daemon 0.6.31-1ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Mon Oct 1 00:05:30 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
Related branches
tags: | added: patch |
Changed in avahi (Debian): | |
status: | Unknown → New |
Changed in avahi (Debian): | |
status: | New → Fix Released |
I have found out what spins up the avahi-daemon. It is the starting of CUPS during boot. So I can reproduce the bug without needing to reboot. I simply run
sudo restart cups
on the command line, repeating this command in the case the avahi daemon does not spin up (it actually spins up in 99% of the cases).
I have 18 print queues which I am sharing and CUPS registers them all with Avahi. One sees them in the "avahi-discover" window under "Internet Printer".