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. > [Unit] > ConditionUser=!Debian-gdm There is also ConditionUser=!@system which should serve a similar/broader purpose, right? > 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 ``` Am Donnerstag, dem 13.03.2025 um 11:55 +0300 schrieb Andrei Borzenkov: > What's wrong with adding After=pulseaudio.service (or whatever this > user service is called)? Nothing's wrong with that, I was just asking for improvements to the service file. Thank you! - Fabian