under systemd avahi-daemon doesn't stay disabled when .local is detected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
avahi (Ubuntu) |
Triaged
|
Medium
|
Trent Lloyd |
Bug Description
When avahi daemon detects .local unicast domain, the daemon is disabled. When a user tries to resolve a domain name through nss, the daemon starts up.
The root cause is most likely in systemd that starts the daemon when an application tries to access the socket through the systemd managed socket file.
This behavior wasn't observed in 14.10 or earlier releases, thus the assumption towards systemd socket activation.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: avahi-daemon 0.6.31-4ubuntu4
ProcVersionSign
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 7 09:51:43 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-16 (506 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: avahi
UpgradeStatus: Upgraded to vivid on 2015-03-18 (19 days ago)
Changed in avahi (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- avahi-daemon doesn't stay disabled when .local is detected + under systemd avahi-daemon doesn't stay disabled when .local is detected |
tags: | added: rls-w-incoming |
Changed in avahi (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
milestone: | none → ubuntu-16.01 |
Changed in avahi (Ubuntu): | |
milestone: | ubuntu-16.01 → ubuntu-16.02 |
Changed in avahi (Ubuntu): | |
assignee: | nobody → Trent Lloyd (lathiat) |
This bug affects the final release of 15.04 and is a regression in regards to 14.10 behavior.