[pulseaudio-discuss] Zeroconf-publish fails to run

Lennart Poettering lennart at poettering.net
Wed Jul 11 17:09:24 PDT 2007

On Sat, 23.06.07 13:25, Rémi Cardona (remi at gentoo.org) wrote:


> > module-zeroconf-publish.c: avahi_entry_group_add_service_strlst():
> > Invalid service name
> > ...
> > 
> > And here is the "s->service_name" on my desktop when calling the
> > previous function:
> > "ALSA PCM on default (ADC Capture/Standard PCM Playback) on stratos"
> > 
> > It looks a lot like bug #39
> > 
> > Going through the whole code with gdb, I can trace this call from pulse
> > down to avahi, down to dbus (that's the further my debugger would go,
> > for some unknown reason) which then returns the error up.
> Status update, I realized that my other box did in fact publish its
> Sink, but not its recording source and neither its server.

This is all probably due to limited maximum DNS-SD service name
length. DNS-SD enforces a maxium service name length of 63 UTF-8
characters. If the name returned by the HW driver is overly long this
results in an invalid string that Avahi refuses the accept.

The fix is easy: just truncate/ellipsize the hw driver name so that the total
size never grows larger than 63 characters.

I updated the bug accordingly an will fix this in PA
eventually. (Unless -- of course -- someone else supplies me with a
patch for this.)


Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

More information about the pulseaudio-discuss mailing list