Avahi services are not updated

Same thing here...

This bug should have been marked as confirmed for a long time....
See https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/116984

@anakin: thank you for for your comment. If you are able to confirm this bug, why not mark it as such? I've set up my system to not using Avahi any more (however still installed because of dependencies).

Takkat > done ;)

There has been an update today for avahi...and I can't reproduce this bug anymore...Takkat > can you confirm ?

Here is still 2.6.25 on Lucid. I cannot reproduce an update. However I did not try Maverick/Avahi 2.6.27 so far. From the changelogs (if any) I didn't see anything related to this admittedly unrecognised bug.

Something very interesting I've just found out...
When I start the computer but do not login to a session...the computer is visible from avahi client
When a user is connected...it is not visible anymore.
So the problem is during gnome startup I guess.

today's update to 2.6.25-1ubuntu6.1 as expected with no success: bug is very present still. Device names are resolved as long as I manually restart avahi-daemon - even if the device has long gone.

Takkat >> and if you don't open any X session...?

Bug still present in a fresh install of ubuntu 10.10..

I have seen this bug in a fresh install of 10.04.1 LTS server edition in the boot console, so I don't think it would be related to any X session.

I have worked around it by making a script called avahi-daemon-restart in /etc/init.d, which consists solely of "sleep 5; restart avahi-daemon". I then used "sudo update-rc.d avahi-daemon-restart defaults" to activate it at startup. (I am not really a Linux pro, so I don't know if this is the most optimal way of doing this, but it worked for me.)

This bug is instantaneously visible if you run it inside VirtualBox (or presumably another virtualizer) under a Mac OS X host. The Mac OS X Finder will show the appearance of the Ubuntu guest as soon as avahi-daemon is restarted, and it vanishes as soon as you shut down the VM.

MacOS should work fine with Bonjour (which is not Avahi). Thanks @Ivan for your workaround. That was ok for me too in respect of initial startup but it does not resolve the IMHO quite serious issue when Avahi still resolves names of devices that are no longer present. I wonder, why so few people seem to be affected.

When thinking of filing an upstream ticket I came across these:

http://avahi.org/ticket/280
http://avahi.org/ticket/229

where it is made clear that Avahi cannot see vanishing services if they don't send a proper good-bye. Won't fix, of course. IMHO however the default time-out for inactive services to disappear seems to be rather long.

avahi daemon is started with upstart...As upstart was introduced recently and I was not able to reproduce this bug under Karmic...it might be related. Look at the /etc/init/avahi-daemon.conf file ;) I'm not familiar with upstart so I can't see anything that might cause this issue...but I'll investigate this further ;)

Here, issue exists in Karmic, Lucid Maverick as well, didn't use Avahi in Jaunty so I don't know.

Takkat >> I may have found another lead on this issue....try to add a txt-record to your service file, like this :

<?xml version="1.0" standalone='no'?><!--*-nxml-*-->
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
<name replace-wildcards="yes">/home</name>
<service>
<type>_sftp-ssh._tcp</type>
<port>22</port>
<txt-record>path=/home/</txt-record>
</service>
</service-group>