© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hmm, that looks OK.
All I can think of is that mt-daapd registers with Avahi after it starts but before it has registed an address record (due to the late DHCP). On my system mt-daapd registers after Avahi has registered addesses.
One would expect Avahi to handle this gracefully but I am not entirely familiar with the protocol. Does restarting mt-daapd rather than Avahi fix the problem?