padevchooser doesn't gracefully handle avahi + multiple network interfaces

[vitaminmoo]

On a machine with five ethernet interfaces (three from vmware, two physical, and one eth0:avahi), when I click on the padevchooser icon, and select "Default Server", I'm seeing ten instances of my hostname. Under "Default Sink" and "Default Source", I'm seeing ten of each sink and source.

I'm not sure why two per interface is showing up, as avahi-discover shows one instance of everything per interface, but it seems logical to only show a single item of each type per unique avahi cookie.

[coling]

Hello,

I get this annoying issue too.

I've "fixed" this in latest stable with this simple patch.

The same patch can apply against latest SVN with minimal hassle.

I did try to take into account the cookie but when the device is removed the cookie is not available so it becomes impossible to match it up on removal.

This will cause issues if there are genuinely separate but duplicated names, but then there will be lots of other issues too in this scenario.

In the case the OP is seeing (with VMWare etc.) I too get this. I did create a patch that appended the new discovered IP address to the IP (or rather "server") already listed for that device if it already exists in the lookup. It did however look a bit ugly so I didn't bother using this one, but feel free to ask if you want it.

Cheers

Col

[rodrigo]

Also, why is padevchooser exiting if avahi-daemon is not running? I think it should just handle that gracefully

[mkbosmans]

padevchooser has been unsupported for many years now. We won't take any bugs/patches for it, so closed as wontfix.