On Fri, Mar 14, 2025 at 1:27 PM Fabian Greffrath <fabian@xxxxxxxxxxxxx> wrote:
Am 2025-03-14 12:18, schrieb Mantas Mikulėnas:
> Depends on whether fluidsynth ever uses the pipewire API directly (in
> which case it should depend on pipewire.service) or whether it always
> goes through the compat shim (in which case it's enough to depend on
> pipewire-pulse.service, as that already indirectly depends on
> pipewire).
It uses either pipewire or pulseaudio directly. I am not sure what it
does if pipewire mimics pulseaudio, but I guess it will still use
pipewire directly in that case.
Then it's probably fine to have it depend on all three .services via Wants+After, I think.
> I think that should work, yes.
Thank you!
> Hmm, I didn't know it uses /run/lock. This is a user service, not a
> system service, right?
Yes, it's a user service. The /run/lock condition is rather new, though,
I haven't seen it before myself:
https://github.com/FluidSynth/fluidsynth/commit/6072fe98395ea575b9e35a3eee0be612bdb277f5
I thought /run/lock was 0755 but I guess that's just an Arch thing...
Mantas Mikulėnas
