FS#36063 - Avahi provides wrong systemd service name

Attached to Project: Arch Linux
Opened by ZRDO (ZRDO) - Sunday, 07 July 2013, 16:13 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 07 July 2013, 19:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: The service name Systemd tries to start is "org.freedesktop.Avahi.service" which doesn't exist and silently fails. The actual service name is "avahi-daemon.service". This sometimes causes systemd-journal to use a high percentage of CPU power because applications try to use the avahi daemon and report the error.

Solution: Either change the systemd default to "avahi-daemon.service" (preferred to keep coherency with other service names) or change the avahi
package service filename to "org.freedesktop.Avahi.service"

Additional info:
extra/avahi 0.6.31-9 x86_64
core/systemd 204-3 x86_64


Steps to reproduce:
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 07 July 2013, 19:50 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Sunday, 07 July 2013, 19:15 GMT
org.freedesktop.Avahi.service is the dbus bus name -- notice the alias in the unit... I can't reproduce whatever bus activation failure spam you're seeing. Have you masked the unit?
Comment by ZRDO (ZRDO) - Sunday, 07 July 2013, 19:31 GMT
Sorry. I was just dumb enough not to research enough before reporting -.-
In a hurry, I confused my actual issue with another different one with the same symptoms and mixed them up. I just troubleshooted this and the issue is pretty much solved, so this was unnecessary.

Again, sorry for the inconvenience: the bug is not so, there was just some corruption in my HD

Loading...