Skip to main content ↑ ↓
Topic: twisted maze of startups or how does pulseaudio start (Read 314 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

twisted maze of startups or how does pulseaudio start

I installed LXDE runit  and was wondering about converting to pure openbox with slim as X11 starter.

Looking at the running apps I see that pulseaudio is started on behalf of the artix user, but I don't know which process starts it.

I don't see an artix user runsvdir and there is no /etc/runit/sv/pulseaudio folder.

So I am wondering who/what starts pulseaudio. In the past I have observed it can be started by something in the XDG folderie one of one of the ~/.config/autostart ~/.config/openbox/autostart, .config/lxsession/LXDE/autostart, /etc/xdg/autostart/pulseaudio.desktop etc  etc.

I know I can always ensure it runs from an openbox-session started openbox, but I notice that sudo root is unable to use espeak so I assume pulseaudio is per user in the existing context.

I have only one set of speakers so why would I not run pulseaudio as a global service. I se that the arch wiki recommends the per user approach.

Re: twisted maze of startups or how does pulseaudio start

Reply #1 –
pulseaudio automagically starts itself. I believe on Arch they moved to starting pulseaudio via systemd sockets instead.
 

Re: twisted maze of startups or how does pulseaudio start

Reply #2 –
Quote from: Dudemanguy – on
pulseaudio automagically starts itself. I believe on Arch they moved to starting pulseaudio via systemd sockets instead.

yes I think I knew/believed that. My question was really about how that's done.  Looking in the /proc/<pid>/environ of the pulseaudio process leads me to believe that it was started via XDG.

From here https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/ it seems it's possible to run as a systemwide service via a unix socket.