GitLab

Greetings,

I am currently testing using pipewire as a replacement for pulseaudio and jack on a linux system that does not use the systemd init system.

As I understand from reading the pipewire documentation, pipewire is designed to be started and managed as a "user target" daemon in the systemd ecosphere. However, this functionality is systemd specific so the problem becomes how to manage pipewire in the absence of systemd.

So far I have just been starting pipewire either manually after a user's dbus session is registered, or with scripts like those in ~/.config/autostart or ~/.xinitrc. This works to start pipewire fine and I can go about using it in audio applications in X or wayland. However, if I logout and terminate the dbus session, the pipewire daemon just gets re-parented to pid-1, with the old dbus address. Starting a new dbus session gets a new address, and that re-parented pipewire isn't reachable and has to be killed manually.

So shouldn't pipewire exit if the dbus no longer exists? Would adding that functionality impact how the pipewire daemon functions in a systemd system? Or, would any of the devs have some other insight on how to properly use pipewire in a non systemd environment?

Thanks,

Bob Funk