[pulseaudio-discuss] [RFC] Add configure option to specify default autospawn behavior

Felipe Sateler fsateler at debian.org
Mon Dec 1 04:23:44 PST 2014

On Mon, Dec 1, 2014 at 5:27 AM, David Henningsson
<david.henningsson at canonical.com> wrote:
> On 2014-11-29 22:04, Felipe Sateler wrote:
>> Dbus integration with systemd user sessions is not complete yet. This
>> means
>> that a socket-activated pulseaudio daemon will not be able to access the
>> session
>> bus, and thus breaking several modules.
>> This means that distributions should not yet enable the systemd units by
>> default
>> until that problem is solved. However, this does not mean that the units
>> cannot be
>> provided for the users that choose to experiment with them.
>> Therefore, I propose to separate the decision to support socket activation
>> from the
>> decision to default to autospawn or not, via a separate configure switch
>>   --enable-autospawn-default. This way one could build socket activation,
>> and not ship
>> it by default.
> One could still do that behaviour by just changing autospawn in
> /etc/pulse/client.conf, right?

Almost. The problem is that if the user has a modified
~/.config/pulse/client.conf, or (on debian-based distros at least) a
modified /etc/pulse/client.conf, they may not get the updated default.

> It looks rather like we need to provide something that builds socket
> activation but disables it? And given the problems we have with socket
> activation (combined with session level D-Bus) maybe it makes sense to
> default to that?

I'm not quite sure what you mean by "disabling it". AFAICT, the
current activation code does fall back to the normal socket opening
when no FD has been passed. So you can have a socket-activated server
running without socket activation.


Felipe Sateler

More information about the pulseaudio-discuss mailing list