[pulseaudio-discuss] [PATCH 7/8] launch: Disable autospawn by default when systemd daemon support is enabled.

[Colin Guthrie]

Tanu Kaskinen wrote on 24/10/14 12:08:
> On Fri, 2014-10-24 at 11:14 +0100, Colin Guthrie wrote:
>> Tanu Kaskinen wrote on 24/10/14 10:42:
>>> "Disable the manual override" doesn't sound like a good idea... Does
>>> this mean that "systemctl --user disable pulseaudio.socket" doesn't
>>> work?
>>
>> Yes, but it also has the advantage that every single user on the system
>> doesn't have to run "systemctl --user enable pulseaudio.socket" before
>> their sound will work. If distros ship this, they will definitely ship
>> this symlink or something similar to it, so I think doing this by
>> default makes sense for us too.
> 
> I expect distros to enable the service only on first install, not on
> package updates.

I expect distros to completely forget this step and then complain -
especially so because this is a user socket unit, not a system on and
the packaging guidelines for such things are still in their relative
infancy.

But I'm not strongly against it, but I just don't like the fact that
this enabling, if done in packaging, would hence be in /etc tree and
thus also suffer from a "factory reset" unless corresponding tmpfiles
rules were also put in place to recreate the symlink.

FWIW, in the downstream usage in Mageia, I have added a
ConditionPathExists= to the pulseaudio.socket to check what the audio
profile is. If the user changes their audio profile to alsa, the socket
does not start.

If you really feel strongly here, I'll remove this rule and include the
[Install] section again, but we really do have to put a really big
warning to distro packagers on how to handle this - I suspect a lot of
them will get it wrong.

>> In this scenario (when the distributor has decided the default action
>> but the user disagrees), "systemctl --user mask pulseaudio.socket" is
>> the recommended approach (as I detailed in the wiki page). See also
>> http://0pointer.de/blog/projects/three-levels-of-off for background on
>> masking.
> 
> Recommended by who? To me it seems strange to have three levels of "off"
> and then making it impossible to use one of them.

One of the reasons that three exist in the first place is to enable this
arrangement, otherwise you'd only need two! :)

But I don't care that much. I know how I'll be doing it downstream (this
way) and I personally think it's sensible and others should do the same,
but I'm not crazy fussed if the upstream way is a bit different.

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/