pipewire-pulse does not always terminate when pipewire is terminated
I noticed two of them lingering: jocke 8233 0.0 0.0 80060 4768 ? S<l 15:43 0:00 /usr/bin/pipewire -c pipewire-pulse.conf jocke 28309 0.0 0.0 82476 7596 ? S<l 10:55 0:00 /usr/bin/pipewire -c pipewire-pulse.conf
I am running openrc and start from pipewire.conf:
context.exec = [
#{ path = <program-name> [ args = "<arguments>" ] }
#
# Execute the given program with arguments.
#
# You can optionally start the session manager here,
# but it is better to start it as a systemd service.
# Run the session manager with -h for options.
#
{ path = "/usr/bin/pipewire-media-session" args = "" }
#
# You can optionally start the pulseaudio-server here as well
# but it is better to start it as a systemd service.
# It can be interesting to start another daemon here that listens
# on another address with the -a option (eg. -a tcp:4713).
#
{ path = "/usr/bin/pipewire" args = "-c pipewire-pulse.conf" }
]
´´´
Edited by Joakim Tjernlund