On Tue, May 31, 2022 at 11:43:06AM +0200, Vincent Lefevre wrote:
> > > > > a) pipewire package enables pipewire service by default
> > > >
> > > > Indeed, but pipewire service doesn't take control of audio over
> > > > pulseaudio. Only pipewire-pulse does that.
> > >
> > > This is incorrect. The pipewire-pulse package was not installed
> > > at all (pipewire-pulse had been installed automatically in
> > > October 2021 due to dependencies, but the change was reverted,
> > > and the package got removed on my machine 3 days later).
>
> Sorry. Actually it got removed because I downgraded the pipewire
> packages back to the previous version (it's clearer with the
> /var/log/apt/term.log* log files).
>
> > > I don't know whether this could cause the issue, but
> > > pipewire-media-session was installed, because pipewire-bin
> > > recommends it. There were already issues with it in the past:
> > What issues?
>
> The ones mentioned below ("Closes: ...").
They are about pipewire-media-session vs wireplumber and/or affect people
installing pipewire-pulse as far as I can see.> > > https://tracker.debian.org/news/1271014/accepted-pipewire-0339-3-source-into-unstable/ > > > which says: > > > > > > * Remove pipewire-media-session from Recommends. > > > (Closes: #995116, #996994, #997859) > > The context of this was "replace pipewire-media-session with wireplumber" > > Indeed, this is what happened with pipewire 0.3.39-1, as I can see > in my dpkg logs and the changelog: > > * Change priority order between pipewire-media-session and wireplumber, > WirePlumber is now the recommended session manager. > > and this is what led to the pipewire-pulse installation. So "pipewire-media-session was installed" is indeed irrelevant. -- WBR, wRAR
signature.asc
Description: PGP signature
