`pipewire` is providing its own replacement for `jack`, so if you are using `pipewire` maybe you should not have `jackd2` installed at all.
I think I've done exactly the following:
```
aptitude --schedule-only install libspa-0.2-jack qsynth rosegarden; aptitude --schedule-only full-upgrade; aptitude install
aptitude purge pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gsettings
aptitude purge qjackctl jackd jackd2
```Then, to start an app needing `jack`, I did:
`pw-jack qsynth` (don't forget to add a soundfont in `settups/soudfounts`)
then:
`rosegarden 28316.mid` (you must go in `studio/manage midi devices` and select a mdi output)
And it worked.
I'm using unstable.
Right after switching to pipewire, I did:
```
aptitude install libspa-0.2-bluetooth pipewire-audio-client-libraries
aptitude purge pipewire-media-session
aptitude reinstall wireplumber
```Maybe as a user you should do:
```
systemctl --user --now disable pulseaudio.service pulseaudio.socket
systemctl --user mask pulseaudio
systemctl --user restart pipewire
```Maybe there should be a dependency conflict between `pipewire `and `jackd`?
Also, concerning
<q cite=""https://wiki.debian.org/PipeWire#For_JACK" rel="noreferrer nofollow noopener" target="_blank">https://wiki.debian.org/PipeWire#For_JACK">
Either run JACK clients using the pw-jack wrapper, or copy:
# cp /usr/share/doc/pipewire/examples/ld.so.conf.d/pipewire-jack-*.conf /etc/ld.so.conf.d/
And run:
# ldconfig
</q>maybe it should be fixed at the debian package level, and hence a bug should be filled against `libspa-0.2-jack`?
I hope it helps,
Chris