On Fri, Mar 14, 2025 at 11:09 AM Fabian Greffrath <fabian@xxxxxxxxxxxxx> wrote:
Am Donnerstag, dem 13.03.2025 um 10:53 +0200 schrieb Mantas Mikulėnas:
> Does Debian support having both Pulseaudio and PipeWire installed at
> the same time? If not, then I *think* you could list both of them in
> Wants= (in addition to After).
I don't think it's possible to have both pipewire and pulseaudio
installed at the same time. But there's also pipewire-pulse which
provides a pulseaudio compatibility shim based on pipewire, not sure
how to take this one into the equation.
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).
> [Unit]
> ConditionUser=!Debian-gdm
There is also
ConditionUser=!@system
which should serve a similar/broader purpose, right?
I think that should work, yes.
> It is a per-user service, so default.target is correct. The per-user
> systemd instances don't have "multi-user.target" (they only run in
> multi-user mode in the first place).
Alright, so you agree a change like this should work?
```patch
--- a/fluidsynth.service.in
+++ b/fluidsynth.service.in
@@ -2,9 +2,11 @@
Description=FluidSynth Daemon
Documentation=man:fluidsynth(1)
After=sound.target
-After=pipewire.service
+After=pipewire.service pulseaudio.service
+Wants=pipewire.service pulseaudio.service
# If you need more than one instance, use `systemctl edit` to override
this:
ConditionPathExists=!/run/lock/fluidsynth.lock
+ConditionUser=!@system
[Service]
# added automatically, for details please see
```
Hmm, I didn't know it uses /run/lock. This is a user service, not a system service, right?
--
Mantas Mikulėnas
