[Pkg-utopia-maintainers] Bug#1025069: pipewire: audio broken, only says Dummy Output (on plain bookworm install)

[Patrice Duroux]

Hi,

I think it would be a shame to come to this: package conflict.

This means that on the same system, their users must exclusively use one same
software and sometimes leaving the decision to the root users (who may also
disagree themselves).
Ideally, it would be even more powerful Debian proposal if, in such a case,
users run whatever in parallel (and without pushing the problem to the container
side). I know that it is not always possible but to consider it is a (big) plus
to me. It also facilite comparison: one time with pulseaudio, one time with
pipewire, without the installing/purging danse. 

A documentation and/or a simple setting command to run that solves is a better
way to my opinion. Could a management script and making the switch be helpful?

Regards,
Patrice

On Tue, 29 Nov 2022 17:51:07 +0100 =?UTF-8?B?RHlsYW4gQcOvc3Np?=
<bob.dybian at gmail.com> wrote:
> Hi,
> 
> Le mar. 29 nov. 2022 à 15:51, Hans-Christoph Steiner <hans at eds.org> a écrit :
> >
> > hans at delbin ~$ sudo journalctl | grep wire
> > ...
> > Nov 26 22:54:40 delbin wireplumber[1092]: stopped by signal: Terminated
> > Nov 26 22:54:40 delbin wireplumber[1092]: disconnected from pipewire
> >
> 
> > Versions of packages pipewire depends on:
> > ...
> > ii  pulseaudio                    16.1+dfsg1-2+b1
> 
> I suspect it is a conflict between pulseaudio and pipewire-pulse and a
> duplicate of
> https://bugs.debian.org/1021530
> 
> Can you check if the pulseaudio service is running? If so, can you try
> to disable (and mask)
> pulseaudio service and socket and restart pipewire, pipewire-pulse and
> wireplumber
> services? These steps are describe at https://wiki.debian.org/PipeWire
> 
> If you are facing this conflict, you can also just remove the
> pulseaudio package. It looks
> like I really have to mark pipewire-pulse in conflict with pulseaudio.
> 
> Best,
> Dylan
> 
>