Open peonerow opened 1 year ago
It's how apt is designed. If you want to remove orphaned packages you have to use the autoremove command or flag.
This ends up leaving both jack2 and pipewire-jack on the system, breaking jack.
If the resulting configuration breaks JACK, then maybe pipewire-jack
should conflict with jackd2
or something?
Worth noting for how this issue is worded, jackd2
is not installed by default; pipewire-jack
is. Does the issue also occur the first time you install jackd2
, or only after installing, removing, and then installing again?
pipewire-jack
is packaged by Pop!_OS in the PipeWire repository, so I'm transferring the issue there. (jackd2
is packaged by Ubuntu; you can see the difference with apt policy pipewire-jack jackd2
.)
Distribution (run
cat /etc/os-release
):Pop!_OS 22.04 LTS
Related Application and/or Package Version (run
apt policy $PACKAGE NAME
):jackd2: Installed: 1.9.20~dfsg-1 Candidate: 1.9.20~dfsg-1 Version table: *** 1.9.20~dfsg-1 500 500 http://apt.pop-os.org/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status
Issue/Bug Description:
Deleting jackd2 with
sudo apt remove jackd2
will install all these packages:jackd1 jackd1-firewire libjack0 libspa-0.2-jack pipewire-jack
. After reinstalling jackd2 withsudo apt install jackd2
the following packages are removed:jackd1 jackd1-firewire libjack0
(notice that pipewire-jack is missing from the list).This ends up leaving both jack2 and pipewire-jack on the system, breaking jack. In my case, the only driver it could access was dummy. Deleting pipewire-jack with
sudo apt remove pipewire-jack
fixes the issue.Steps to reproduce (if you know):
(I don't know if the system originally comes with pipewire-jack or jackd2, but I will assume that it's jackd2)
sudo apt remove jackd2
sudo apt install jackd2
Expected behavior:
pipewire-jack taking priority over jackd2, making it unable to see any drivers like ALSA.
Other Notes:
Seems like an oversight. Additionally I don't know it's a debian/ubuntu repository issue. I encountered it on Pop, so that's why I'm reporting it here.