1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.KDE

  • Pipewire in testing ?

    From Erwan David@21:1/5 to All on Tue Feb 4 10:40:01 2025
    I saw today that I have those 4 lines repeating continuously (every 5
    seconds)

    Feb 04 10:25:19 maine-ocean plasmashell[2348]: pw.conf: can't load
    config client.conf: No such file or directory
    Feb 04 10:25:19 maine-ocean plasmashell[2348]: pw.conf: can't load
    config client.conf: No such file or directory
    Feb 04 10:25:19 maine-ocean plasmashell[2348]: kpipewire_logging: Failed
    to create PipeWire context
    Feb 04 10:25:19 maine-ocean plasmashell[2348]: received error while
    creating the stream "Failed to create PipeWire context" Media monitor
    will not work.

    Does this mean that there is an ongoing transition to pipewire ? And
    what should I do ?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Erwan David@21:1/5 to Shmerl on Wed Feb 12 10:20:01 2025
    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.

    If you are still not somehow, make sure to install pipewire and pipewire-pulse,
    and remove all pulseaudio / pulseaudio-* packages.

    You might also want libspa-0.2-bluetooth for bluetooth.
    Look around for more pipewire packages depending on what you need.

    And that's all is needed ? I am not proficient in sound thus, I fear thus bugs.

    --
    Erwan David

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Steigerwald@21:1/5 to [email protected] on Wed Feb 12 16:20:03 2025
    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,
    --
    Martin - please no carbon copy to me

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Erwan David on Wed Feb 12 19:10:01 2025
    On Wed, Feb 12, 2025 at 06:56:04PM +0100, Erwan David wrote:
    And that's all is needed ? I am not proficient in sound thus, I fear thus bugs.

    https://wiki.debian.org/PipeWire https://wiki.archlinux.org/title/PipeWire
    https://packages.debian.org/search?suite=trixie&keywords=pipewire


    I see that pipewire-audio should be Ok for me, but I see in the archwiki
    that pwvucontrol replaces pavucontrol. But it is not available in debian. Will pavucontrol still work ?

    Yes, all tools including the KDE mixer work with both.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmes4eUtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh rbMP/2wcvBqUEGLYv2D52S30Mg77F0rZh+Tj6XC3jwvlBmtSsaGGN9xaSRWhAVOV vqHiLrzYzl5bYHGSP6H4Rizn+XxTkyYmBJvbqPjYmrdyZQMw8oXetcJqvB2ReMui 8U3EVvET0xvxHtTdbt3j5V56J3IPHdHXGiQ/gEN6DA4WtEzCMa7f52rhv9dFDcrH ZwH/PnVkzJzav6TqAhUCtHavJgECnVA7NPWfHfE6Cpua14CETCmH+nlBxQPhMs/f DRi3zOxvOMe734/aw5woJgsPtZgq5xxVieYFX4seoYucs3GrAx8ObVBExwz7KkFC gsKYl1v4Ui9GeQkVQtTSdK4o8le7DU8l0dOAiSAaw+zqtd0qm543P8TvEXFaH0ki iB4NjQlOxWtMyHhCEW4+am9eRNdNNn1d6H68Xde6HNPjDklBMfrNhvY+wxxA1qfE +IEYEsiNEg9SK3tx6a3SWtDLPlmCmgdw0nHWLDWNxy4PKl37Q7MxyxTWzvY0JZ3R UfULV1ffyufRBS71dhK6e0TKTROESLs4E9XnMtk6UQ9vT9Ag31XR+FHUd939VCzY NC6zP+8nZHpzly6C3gu8guDNvdcFSI+Oq5By2w9qBI1jNyC3uMcx8oQ9QzaTbBQs 0sYcSGVOMVK0lbufUnKMI+y2nu6aSDbR4I/pAaZULJ72JmkY
    =dM6u
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Erwan David@21:1/5 to All on Wed Feb 12 19:10:01 2025
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)