Thanks, that's fair enough.

My remaining questions then are:

1. Why is /usr/bin/start-pulseaudio needed?
2. Why is /etc/pulse/client.conf ignored?
3. In light of 2, why is /etc/pulse/client.conf.d/01-respawn-something needed?
4. And in light of /lib/systemd/user/pulseaudio.service, why is 
/etc/xdg/autostart/pulseaudio.desktop needed?

Wouldn't one way to start pulseaudio be sufficient? Also, please don't
ignore the configuration.

Finally, how can I use any of these methods to start pulseaudio in
system mode? Adding -D to /lib/systemd/user/pulseaudio.service did not
work (probably because I'm not root).

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.

  Pulseaudio cannot be kept from starting or respawning

Status in pulseaudio package in Ubuntu:

Bug description:
  On my freshly installed system, I need to run pulseaudio in system
  mode.  Alas, by default, pulseaudio is run in user mode, and is set to
  respawn, so that I cannot kill the user process and start pulseaudio
  in system mode.

  I tried:

  1. Editing /etc/pulse/client.conf, setting autospawn = no.  This did nothing.
  2. Removing the file /etc/pulse/client.conf.d/01-respawn-something.  I cannot 
even begin to fathom why such a file would exist.  Anyway, this did nothing.
  3. I removed the file /usr/bin/start-pulseaudio.  Why ....  Of course, this 
did nothing.
  4. I removed the file /etc/xdg/autostart/pulseaudio.desktop.  Why on earth do 
you implement four different ways to annoy your users?  On the other hand, this 

  User mode is still starting, and respawning is enabled.

  What the heck do I have to do to get rid of user mode pulseaudio?
  Could you please clean up this clusterfuck?

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to