On Mon, Dec 8, 2014 at 8:57 AM, Tanu Kaskinen <tanu.kaskinen at linux.intel.com> wrote: > > On Mon, 2014-12-01 at 13:18 -0300, Felipe Sateler wrote: > > On Mon, Dec 1, 2014 at 10:55 AM, David Henningsson > > <david.henningsson at canonical.com> wrote: > > > So, excuse me if this comes from a systemd newbie. But here's my reasoning: > > > > > > As of now, we have seen some reduced functionality because PulseAudio can't > > > access D-Bus. (And we don't know how far D-Bus is from moving from > > > per-session to per-user, so we assume the bus is per session for now.) > > > > > > This means that at least module-jackdbus-detect and the device reservation > > > protocol are regressed. I don't know what implications the lack of > > > server-lookup has. module-dbus-protocol is also broken, but that module is > > > (AFAIK) still broken in other ways too. > > > > > > Let's then assume we think this is severe enough not to recommend people to > > > use systemd activation by default, because all distros I know of have > > > already removed it. > > > > > > Then our upstream default becomes: > > > * Ship with autospawn=yes > > > * Ship with files for enabling systemd activation > > > * Ship without "systemctl --global enable pulseaudio.socket" (if that's the > > > same as building it in, but not enabling it). > > > > > > In essence, if we ship without "systemctl --global enable pulseaudio.socket" > > > already, the only difference we need to do is to re-enable autospawning even > > > if systemd activation is built in. (In an ideal world, the "systemctl > > > --global enable pulseaudio.socket" should also disable autospawning...) > > > > > > Would that not give what Felipe is after, i e, building it in for people > > > that want to experiment, but have it remain disabled? > > > > The only difference between your proposal and my patch is that the > > default would not be configurable. But if the default is the same that > > I want (autospawn = true) then I'm ok with that too :) > > (Disclaimer: I might not have read follow-up messages if they were sent > to another thread.) I think the best way forward would be to do as David > suggested, i.e. don't bother with adding a configure option. If I > understood correctly, we just need to change the default autospawn value > to be always "yes". Would you be willing to write a patch for that? > (Another disclaimer: perhaps someone sent such patch already, but I > didn't notice it yet, since I'm reading mails in oldest-first order.) There has been no patches yet. But reverting commit 7276faca should go back to the autospawn = true behavior, as that was the only change in that commit. The wiki page that says socket activation is the preferred way[1] should be modified as well. [1] http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Running/ -- Saludos, Felipe Sateler
