Re: Pipewire in testing ?
Erwan David <[email protected]>
| Newsgroups | gmane.linux.debian.user.kde |
|---|---|
| Message-ID | <[email protected]> |
Le 12/02/2025 à 16:15, Martin Steigerwald a écrit : > Hi Erwan, hi Shmerl, > > Erwan David - 12.02.25, 10:17:00 MEZ: >> On Wed, Feb 12, 2025 at 05:18:00AM CET, Shmerl > <[email protected]> said: >>> Any reason you aren't already using pipewire? >> Yes : I installed before pipewire was available, and waited for KDE to >> switch. > Plasma switched already. Do you have pipewire processes running? > > ps aux | grep pipewire > > Should be automatically started with Systemd. > > (I use Runit and so had to make sure it is started by other means.) > > In addition to the pipewire packages Shmerl mentioned I also made sure > wireplumber is installed. "wpctl status" should give you a nice overview > over your sound devices and audio clients. Might be a good way to verify > on command line whether Pipewire is working for you. > > I am not sure whether wireplumber is required, but at least it does not > seem to cause any harm and audio is just working very fine for me. > > Best, Thanks every body. I installed the meta package pipewire-audio and vlc-plugin-pipewire (not sure if it was necessary) I could not test bluetooth yet, but it seems to work.