[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1038627: general: Various applications log PipeWire-related errors on a Bookworm system using PulseAudio.



Thank you for the repsonse, Simon! 

Should the pipewire service be left enabled, or it's better to disable it after the pipewire and wireplumber packages are installed? Will it cause conflicts with PulseAudio if both are enabled?

Yura

------- Original Message -------
On Monday, June 19th, 2023 at 13:08, Simon McVittie - smcv at debian.org <wudqerpmidpvhsjwveshtwwhsrmsbrgscm@simplelogin.co> wrote:


> On Mon, 19 Jun 2023 at 10:47:49 +0300, Yura wrote:
> 
> > After upgrade to Bookworm, due to certain limitations of the current
> > PipeWire implementation I had to switch to PulseAudio. The switch was
> > done by installing pulseaudio package, deleting all PipeWire packages and
> > finally enabling pulseaudio service on a user level.
> 
> 
> Pipewire is not just for audio, it's also used for video capture
> (that's why xdg-desktop-portal needs it, and the same is probably true
> for other applications).
> 
> To disable the audio side of Pipewire, my understanding is that it should
> be sufficient to remove pipewire-pulse, pipewire-alsa, pipewire-jack
> and libspa-0.2-bluetooth, while leaving pipewire and wireplumber installed.
> 
> smcv


Reply to: