The package "pulseaudio" contains the files: /usr/bin/start-pulseaudio-x11 /etc/pulse/client.conf.d/01-enable-autospawn.conf
Thus, it should be fairly obvious where I got the files from. And /etc/pulse/client.conf is ignored, despite my user (and root) not having a ~/.local/pulse directory. And why would we need files for non-systemd systems if Ubuntu _is_ a systemd-base system? So I still think something is quite wrong with the pulseaudio package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899352 Title: Pulseaudio cannot be kept from starting or respawning Status in pulseaudio package in Ubuntu: Invalid 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 did NOTHING. 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: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp